-
-
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
[WIP] Blin 2019-08-20 #3132
Comments
There's a golf for c7056f2 issues here: c7056f2#commitcomment-34749749 |
@AlexDaniel, |
Yes, got that! Thank you! |
From the last Blin run:
Ping @vrurg. Blin output: https://usercontent.irccloud-cdn.com/file/FuRvVGH3/blin-output-2019-08-29.tar.gz
There are many modules depending on YAMLish, but YAMLish was bisected to a different commit (c7056f2), but issues in that commit were already fixed, so it's just a bisection detail. |
About 43066b9, I mentioned when the 6.e grammar base class was being discussed that there should also be another meta-class (a 6.e GrammarHOW), which the 6.e BOOTSTRAP can then configure with the 6.e Grammar. That meta-class can go either in BOOTSTRAP or even in the 6.e setting. That would avoid this issue. Trying to do it with the approach taken here is not going to end well. |
I think they're all because we find the wrong
Why? If we did that, we'd not have the problem exhibited here. And, more deeply, it feels entirely right to me: the default parent is a meta-behavior, and if we're already having another version of a behavior, I don't see why we shouldn't have another version of the related meta-behavior too. |
Aha. I had to limit symbol lookup to setting, but used lexical lookup on client.
Language-specific meta? Should be possible, but not yet supported by the build subsystem. I have started process of merging common parts of moar and jvm makefiles and it turns out to be even more time consuming than I expected. But otherwise the first thing coming to my mind is |
|
#3154 fixes all reported modules except for |
Thank you, @vrurg! Please take care. |
It must be possible to create grammars named `Grammar` rakudo/rakudo#3132
It must be possible to create grammars named `Grammar` rakudo/rakudo#3132
|
All failures fixed with c757ada and with the above mentioned PR. |
Test for 6.e grammar `Grammar` name It must be possible to create grammars named `Grammar` rakudo/rakudo#3132
Here are the latest results. Seems previous issues are not resolved? @vrurg, can you check? Raw data: https://usercontent.irccloud-cdn.com/file/WWEU5lHe/blin-output-2019-09-06.tar.gz
|
@AlexDaniel check if it was ran against
There must be something else. |
@vrurg thank you for your work! It's time for a new ticket. |
All these should be fixed with 0dd6573:
Raw Blin files: https://usercontent.irccloud-cdn.com/file/Kuaq7HLm/blin-output-2019-08-20.tar.gz
Previous ticket: #3113
From the previous ticket (we need to figure out what was wrong there anyway):
The text was updated successfully, but these errors were encountered: