A change list for the compiler #59938
Open
+35
−0
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
This is great, thank you. I think it should probably go in devdocs? |
|
Since this is meant to be like |
|
OK I guess this is fine. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Changes to the compiler in 1.12, while very welcome, caused work for some packages that interface with the compiler. I'm aware of chalk-lab/Mooncake.jl#714 and TuringLang/Libtask.jl#196, there are probably others. This is of course understandable and unavoidable when packages interface with internals that aren't public.
However, as discussed on Slack a few times, it would be very useful for package maintainers if there was even a rough list of changes, and advice on how to adapt to them. To kickstart this, I started a draft with changes I encountered in 1.12. It is very incomplete (reflecting my very superficial understanding of the compiler), and I would be grateful and happy if those who know this stuff better would be up for completing it, merging it, and adding to it as more things happen in 1.13.