Skip to content
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

use invokelatest to check for binding existance after evaling a package load #95

Merged
merged 1 commit into from
Mar 14, 2025

Conversation

KristofferC
Copy link
Member

No description provided.

Copy link
Member

@oxinabox oxinabox left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Oh cool, we are now solving isdefined at compile-time?

@KristofferC
Copy link
Member Author

I don't think the isdefined check happens at compile time but the visibility of a binding is now only in a certain world age range so if you introduce a new binding (like when loading a package) you need to either hit top-level or use invokelatest (in the same way as if you would have defined a new method in local scope).

@oxinabox oxinabox merged commit 21937b7 into main Mar 14, 2025
52 of 65 checks passed
@oxinabox oxinabox deleted the kc/binding branch March 14, 2025 01:35
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