Skip to content

Conversation

@timholy
Copy link
Member

@timholy timholy commented Nov 25, 2020

Based on poking around Julia's src/dump.c, it's my understanding
that a disconnected (backedge-free) MethodInstance needs to be
cached in the module owning the Method.
The implication is that Base methods that get called on
package-defined objects cannot be cached on their own merits, so we
should exclude such MethodInstances.

The way to fix this is to make such calls inferrable,
in which case they will be cached in the package module thanks to
their backedges.

Based on poking around Julia's `src/dump.c`, it's my understanding
that a *disconnected* (backedge-free) `MethodInstance` needs to be
cached in the module owning the `Method`.
The implication is that Base methods that get called on
package-defined objects cannot be cached on their own merits, so we
should exclude such `MethodInstance`s.

The way to fix this is to make such calls inferrable,
in which case they will be cached in the package module thanks to
their backedges.
@timholy timholy merged commit 65b4924 into master Nov 25, 2020
@timholy timholy deleted the teh/ownership branch November 25, 2020 16:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants