-
Notifications
You must be signed in to change notification settings - Fork 25
changes/simplifications/bugfixes to support v1.12 #147
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
Open
vtjnash
wants to merge
5
commits into
JuliaDynamics:master
Choose a base branch
from
vtjnash:jn/correct-edges-1.12
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
Show all changes
5 commits
Select commit
Hold shift + click to select a range
c57f5bb
changes/simplifications/bugfixes to support v1.12
vtjnash ce70cf9
Merge branch 'master' into jn/correct-edges-1.12
Krastanov 588df33
relax explicitimports
Krastanov a6de1d1
comment out poorly done ExplicitImports test
Krastanov af357f8
fix CI on branch
vtjnash File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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 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 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 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
Oops, something went wrong.
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.
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.
Something to consider after this PR: this pre-work analysis here is invalid now that binding replacement is possible. Does it provide any useful result, or can this just be deleted (along with all of the associated complexity it causes)?
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.
Supposedly much of this complexity was necessary for the generated coroutine to be fast. Without all of this, the generated structure representing the finite state machine did not have its fields concretely typed, leading to a ton of boxing and allocations.
Or maybe I am completely misunderstanding. Regrettably, currently I am the only "maintainer", but I myself am not particularly knowledgeable of the compiler internals that this package depends on. Maybe more of a "care taker" than a "maintainer".
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.
Gotcha. Yeah, I did some git splunking and it appears that this should have been removed in #76, but apparently got left behind as detritus of the original design limitations. I'll take that as license to clean this up more.
I am interested in helping maintain this, particularly as an example project of how to use the compiler internals well. I have some ideas in mind for more drastic improvements.