|
🦋 Welcome to the IRC channel of the core developers of the Raku Programming Language (raku.org #rakulang). This channel is logged for the purpose of history keeping about its development | evalbot usage: 'm: say 3;' or /msg camelia m: ... | Logs available at irclogs.raku.org/raku-dev/live.html | For MoarVM see #moarvm Set by lizmat on 8 June 2022. |
|||||||||||||||||||||||||||||||||||||||
|
00:00
reportable6 left
00:02
reportable6 joined
00:44
Voldenet left,
Voldenet joined
02:33
committable6 left,
linkable6 left,
sourceable6 left,
statisfiable6 left,
benchable6 left,
bisectable6 left,
quotable6 left,
squashable6 left,
unicodable6 left,
coverable6 left,
releasable6 left,
bloatable6 left,
tellable6 left,
shareable6 left,
greppable6 left,
notable6 left,
evalable6 left,
nativecallable6 left,
reportable6 left
02:34
quotable6 joined,
reportable6 joined,
evalable6 joined,
coverable6 joined,
shareable6 joined,
linkable6 joined,
benchable6 joined,
unicodable6 joined
02:35
committable6 joined,
notable6 joined,
tellable6 joined,
greppable6 joined,
nativecallable6 joined,
bloatable6 joined,
sourceable6 joined,
bisectable6 joined
02:36
statisfiable6 joined,
squashable6 joined,
releasable6 joined
04:40
quotable6 left,
statisfiable6 left,
reportable6 left,
bisectable6 left,
evalable6 left,
committable6 left,
nativecallable6 left,
greppable6 left,
benchable6 left,
tellable6 left,
notable6 left,
sourceable6 left,
shareable6 left,
linkable6 left,
unicodable6 left,
coverable6 left,
squashable6 left,
releasable6 left,
bloatable6 left,
evalable6 joined,
unicodable6 joined
04:41
quotable6 joined,
committable6 joined,
benchable6 joined,
notable6 joined,
tellable6 joined,
coverable6 joined
04:42
squashable6 joined,
bisectable6 joined,
bloatable6 joined,
reportable6 joined,
releasable6 joined,
statisfiable6 joined
04:43
linkable6 joined,
nativecallable6 joined,
shareable6 joined,
greppable6 joined,
sourceable6 joined
05:43
reportable6 left,
evalable6 left,
tellable6 left,
committable6 left,
bloatable6 left,
unicodable6 left,
greppable6 left,
notable6 left,
sourceable6 left,
shareable6 left,
statisfiable6 left,
nativecallable6 left,
benchable6 left,
quotable6 left,
coverable6 left,
linkable6 left,
bisectable6 left,
releasable6 left
05:44
committable6 joined,
evalable6 joined,
unicodable6 joined,
benchable6 joined,
shareable6 joined,
sourceable6 joined
05:45
tellable6 joined,
releasable6 joined,
reportable6 joined,
greppable6 joined,
linkable6 joined,
statisfiable6 joined,
quotable6 joined,
coverable6 joined
05:46
nativecallable6 joined,
bloatable6 joined,
bisectable6 joined,
notable6 joined
06:00
reportable6 left
06:02
reportable6 joined
|
|||||||||||||||||||||||||||||||||||||||
| nine | Why wouldn't they be? You already have a resolver. That can give you those exception classes | 07:53 | |||||||||||||||||||||||||||||||||||||
|
10:41
evalable6 left,
linkable6 left
10:42
linkable6 joined
10:43
evalable6 joined
11:01
ab5tract joined
|
|||||||||||||||||||||||||||||||||||||||
| ab5tract | nine: Any other low-hanging fruit that for RakuAST that you aren't working on? | 11:02 | |||||||||||||||||||||||||||||||||||||
| lizmat | fwiw, I'm working on RakuAST::Type::Setting to actually do a setting lookup only | 11:04 | |||||||||||||||||||||||||||||||||||||
| which has some interesting bootstrap issues | |||||||||||||||||||||||||||||||||||||||
| ab5tract | lizmat++ | 11:15 | |||||||||||||||||||||||||||||||||||||
| Bootstrap Issues == Implementor Torment Inevitable | |||||||||||||||||||||||||||||||||||||||
|
11:37
ab5tract left
|
|||||||||||||||||||||||||||||||||||||||
| Geth | rakudo/main: bc481335ba | (Elizabeth Mattijsen)++ | 2 files RakuAST: make single part setting lookups work The multi-part one still fails, but that's code in the resolver that will need closer scrutiny |
11:42 | |||||||||||||||||||||||||||||||||||||
| lizmat | afk& | ||||||||||||||||||||||||||||||||||||||
|
11:45
sena_kun joined
11:56
ab5tract joined
12:00
reportable6 left
12:01
timo1 left
12:02
reportable6 joined
12:07
ab5tract left
12:08
timo1 joined
12:15
ab5tract joined
12:38
ab5tract left,
ab5tract joined
13:09
ab5tract left
13:13
ab5tract joined
|
|||||||||||||||||||||||||||||||||||||||
| [Coke] | any pointers on how to do the lookup? | 13:19 | |||||||||||||||||||||||||||||||||||||
| I tried copycatting some others (was on a different laptop so I don't have the exact code), but my attempts compiled but failed to find the class. | 13:22 | ||||||||||||||||||||||||||||||||||||||
|
13:24
timo1 left,
timo1 joined
|
|||||||||||||||||||||||||||||||||||||||
| nine | ab5tract: I don't know about low hanging. But I'd love for someone to take charge on POD. | 13:29 | |||||||||||||||||||||||||||||||||||||
| Nemokosch | Are the nodes also missing? | 13:50 | |||||||||||||||||||||||||||||||||||||
|
14:12
ab5tract left
14:35
ab5tract joined
14:48
patrickb left
14:51
patrickb joined
15:03
ab5tract left
15:17
ab5tract joined
15:50
patrickb left
15:56
patrickb joined
|
|||||||||||||||||||||||||||||||||||||||
| lizmat | m: my class IO::Path { }; dd MY::<IO>.HOW<Path>.^methods.elems # I sorta expected to see 1 here (for BUILDALL) | 16:28 | |||||||||||||||||||||||||||||||||||||
| camelia | 87 | ||||||||||||||||||||||||||||||||||||||
| lizmat | nine vrurg ^^ is that to be expected? | ||||||||||||||||||||||||||||||||||||||
| in other words: we cannot lexically shadow multi part names? | 16:29 | ||||||||||||||||||||||||||||||||||||||
| m: my class IO::Path { }; dd MY::<IO>.HOW<Path> # looks like ^methods falls back to the setting ? | 16:33 | ||||||||||||||||||||||||||||||||||||||
| camelia | Failure.new(exception => X::AdHoc.new(payload => "Type Perl6::Metamodel::ClassHOW does not support associative indexing."), backtrace => Backtrace.new) | ||||||||||||||||||||||||||||||||||||||
| lizmat | argh | ||||||||||||||||||||||||||||||||||||||
| argh HOW/WHO mixup again | 16:34 | ||||||||||||||||||||||||||||||||||||||
| [Tux] |
|
16:43 | |||||||||||||||||||||||||||||||||||||
|
16:43
ab5tract left
16:45
ab5tract joined
17:12
japhb left
17:22
codesections left
17:23
japhb joined
|
|||||||||||||||||||||||||||||||||||||||
| lizmat | m: my class IO::Path { }; dd IO::Path.WHERE; dd IO.WHO<Path>.WHERE; dd SETTING::<IO>.WHO<Path>.WHERE # nine vrurg shouldn't that last one be different ? | 17:46 | |||||||||||||||||||||||||||||||||||||
| camelia | 2924936958752 2924936958752 2924936958752 |
||||||||||||||||||||||||||||||||||||||
|
18:00
reportable6 left
18:03
reportable6 joined
|
|||||||||||||||||||||||||||||||||||||||
| lizmat | m: BEGIN dd IO::Path.WHERE; my class IO::Path { }; dd IO::Path.WHERE; dd IO.WHO<Path>.WHERE; dd SETTING::<IO>.WHO<Path>.WHERE | 18:31 | |||||||||||||||||||||||||||||||||||||
| camelia | 3881366585920 3881419809824 3881419809824 3881419809824 |
||||||||||||||||||||||||||||||||||||||
| lizmat | more extensive: the first one is the one from the setting, the last one is the local one, which it shouldn't be ? | ||||||||||||||||||||||||||||||||||||||
| since this is broken with the current grammar as well, I'm not going to be spending more time on that now | 18:34 | ||||||||||||||||||||||||||||||||||||||
| vrurg | lizmat: it's not broken. You override IO namespace. | 18:46 | |||||||||||||||||||||||||||||||||||||
| Geth | rakudo/main: 3a9c1540de | (Elizabeth Mattijsen)++ | src/Raku/ast/resolver.rakumod RakuAST: streamline constant lookup in resolver Specifically the IMPL-RESOLVE-NAME-CONSTANT method, with reduction of duplicated code, and support for partial lookups added. The IMPL-PARTIALLY-RESOLVE-NAME-CONSTANT method is removed. ... (18 more lines) |
||||||||||||||||||||||||||||||||||||||
| vrurg | I mean, it's not a bug with SETTING::, it's a bug with my-scoping of multi-part declarations. | 18:47 | |||||||||||||||||||||||||||||||||||||
| lizmat | well, it's not a bug in RakuAST, so I won't be spending any time on it further for now | ||||||||||||||||||||||||||||||||||||||
| afk& | 18:48 | ||||||||||||||||||||||||||||||||||||||
| vrurg | Likely so. | ||||||||||||||||||||||||||||||||||||||
| tbrowder__ | I'm working on a calendar module, and Isee a need for a couple of missing methods on the Dateish role. if I'm not mistaken, there is no routine for giving the total number of full and partial weeks in a month. in the Gregorian calendar. That would be the number of rows shown in a conventional monthly calendar layout. | 20:09 | |||||||||||||||||||||||||||||||||||||
| I would be happy to file a Rakudo issue and take on the PR if there is any support for the idea. | 20:10 | ||||||||||||||||||||||||||||||||||||||
| in the meantime i will add them to my Date::Utils module | 20:12 | ||||||||||||||||||||||||||||||||||||||
| [Coke] | I don't think that needs to be in core, my 2¢ | 20:34 | |||||||||||||||||||||||||||||||||||||
|
20:45
timo1 left
20:46
timo1 joined
|
|||||||||||||||||||||||||||||||||||||||
| nine | Multi part names and lexicals don't mix well. As the stash that final symbol will installed into may be a global. | 21:08 | |||||||||||||||||||||||||||||||||||||
| lizmat: I have thought on and off about this since I first discovered this behavior, but haven't come up with any alternative that would work better. I often arrive at "maybe Perl actually did this right", i.e. that nested stashes are maybe not worth it. But then, apparently in real-life code it doesn't really cause problems either. | 21:12 | ||||||||||||||||||||||||||||||||||||||
|
21:14
djinni` left
21:22
sena_kun left
|
|||||||||||||||||||||||||||||||||||||||
| vrurg | I thought that perhaps it would be better to install symbols in lexical scope. This would then require duplicating the whole IO namespace into the lexical scope. Never got to the point of considering all possible side effects and problem though. | 21:32 | |||||||||||||||||||||||||||||||||||||
|
21:36
djinni` joined
|
|||||||||||||||||||||||||||||||||||||||