This repository has been archived by the owner on Jan 2, 2021. It is now read-only.
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.
Switch back to bytecode #873
Switch back to bytecode #873
Changes from all commits
52e0e7c
aa3fae1
86a1375
63a4a44
9903b7f
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
Do we want
GetModIface
andGetModIfaceWithoutLinkable
,or
GetModIface
andGetModIfaceWithLinkable
?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.
I don't know, this way is more consistent with
GetModIface
andGetModIfaceWithoutTimestamps
. If you feel otherwise, we can change it.The only place where it makes a difference is when defining new
Rules
(since it can save recomputation if the linkable changed but the iface hash remained the same). If it is justuse
d withrunIdeAction
or something, then there shouldn't be any difference.