-
-
Notifications
You must be signed in to change notification settings - Fork 373
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
Can't require package with globally existing classnames #4488
Comments
My hunch is this behavior is related to #2789 since it (the noted behavior/error) was not in the 2019.03.1 release but started for the 2019.07 release onward which corresponds with when that PR was merged |
Fix is incoming, pending spectests |
ugexe
added a commit
to ugexe/zef
that referenced
this issue
Aug 25, 2021
@tony-o did this get fixed? |
@Leont forgot to push the fix. Will merge once spectest finishes |
@Leont this is merged in master - |
codesections
pushed a commit
to codesections-forks/rakudo
that referenced
this issue
Nov 7, 2021
* bug fix for rakudo#4488
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The Problem
Given this
Foo.rakumod
:These will work:
raku -e 'use Foo'
raku -e 'need Foo'
raku -e 'require ::("Foo")'
but this will not:
raku -e 'require Foo'
My guess would be that this related to the placeholder package that require installs.
Environment
The text was updated successfully, but these errors were encountered: