-
-
Notifications
You must be signed in to change notification settings - Fork 5.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Finalizers take function as first argument (closes #16307) #24605
Changes from 5 commits
b0bf9c2
747444b
1534c38
687e86a
1c3b17a
03ff4fb
f94d5c9
9516d83
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -267,7 +267,13 @@ This section lists changes that do not have deprecation warnings. | |
* The return type of `reinterpret` has changed to `ReinterpretArray`. `reinterpret` on sparse | ||
arrays has been discontinued. | ||
|
||
* `Base.find_in_path` is now `Base.find_package` or `Base.find_source_file` ([#24320]) | ||
* `Base.find_in_path` is now `Base.find_package` or `Base.find_source_file` ([#24320]). | ||
|
||
* `finalizer` now takes functions or pointers as its first argument, and the object being | ||
finalized as its second (rather than the reverse). For the majorities of uses cases this | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. "For the majority of use cases, this change will..." |
||
will trigger deprecation warnings. However, it will not if the 'function' is not a | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. "However, this change will not trigger deprecation warnings where: (1) the callable argument is not a subtype of |
||
subtype of `Function`, nor will it for the ambiguous cases where both arguments are | ||
`Function`s or `Ptr{Void}`s ([#24605]). | ||
|
||
Library improvements | ||
-------------------- | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
All of these lines have trailing whitespace, which is causing the CI failures. (It looks like we forgot to set up
make check-whitespace
on Circle CI.)