🦋 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.
Geth rakudo/main: bfc5af695e | (Elizabeth Mattijsen)++ | 2 files
Make reverse/unlink/rmdir complain when called w/o arguments

Note that this does not affect them being called with an empty array. That's fine.		 10:30
rakudo/main: c1f7e4d488 | (Elizabeth Mattijsen)++ | src/Raku/Grammar.nqp
RakuAST: add sorry for use of say/put/print w/o args

This is a reduced version of the logic that exists in the legacy grammar, which think we shouldn't copy over to the Raku grammar.
The reason I'm adding this check for say/put/print, is that they would be the most common cases, **and** there is a spectest for at last a bare "put". But frankly, I'd rather get rid of this all.		 11:33
lizmat +1
lizmat so now at 918
nemokosch that's quite a lot 13:22
github.com/Raku/doc-website/discus...nt-6708598 could be of interest 13:23
ugexe oh i didn't realize we did stuff like allow `unlink(@multiple-files` which A) isnt immediately clear what happens when one of the files fails to unlink, as well as it returns an array(!) 13:29
also seems odd that it doesn't return Array[IO::Path], but instead Array[IO::Path|Str] 13:31
its been like this since forever though 13:32
m: say unlink("asdfasfasdf") 13:34
camelia [asdfasfasdf]
ugexe eh, that isn't useful 13:35
it should fail, return false, return empty, anything but return the file it definitely did not delete
Geth rakudo/lizmat-WHERE-WHICH-WHO: 991678cd4f | (Elizabeth Mattijsen)++ | 10 files
Add sub versions of WHERE WHICH WHO

They seem to have been forgotten, but are actually mentioned in some error messages. Feels they should be added for completeness sake. Also adapts tests accordingly.		 17:30
rakudo/main: dbde821f99 | (Elizabeth Mattijsen)++ (committed using GitHub Web editor) | 10 files
Add sub versions of WHERE WHICH WHO (#5336)

They seem to have been forgotten, but are actually mentioned in some error messages. Feels they should be added for completeness sake. Also adapts tests accordingly.
Geth rakudo/main: 7bc98ec415 | (Elizabeth Mattijsen)++ | 2 files
Add HOW/VAR/WHAT/WHO as Mu methods

For introspection, and to allow them to be called with foo."$bar"() syntax. Also adapt one test that now also suggests VAR.		 18:14
lizmat I'm getting *really* confused now :-) 21:50
m: dd Rat.new(-1,0) # all ok, also under RakuAST 21:51
camelia <-1/0>
lizmat m: dd Rat.new(-1,0).Num # -Inf with legacy, Inf with RakuAST
camelia -Inf
lizmat m: use nqp; dd nqp::div_In(-1,0) # ok under legacy *and* RakuAST 21:53
camelia -Inf
lizmat I've adapted Rational.Num to show the values of $!numerator and $!denominator are correct and they are 21:54
yet, in that case nqp::div_In(-1,0) returns Inf rather than -Inf under RakuAST
fixing this is +2 on the number of passing test files for RakuAST 21:55
nine ^^ ideas ? I'm out apart from adapting Rational.Num to check specifically for $!denominator == 0 and then do "manual" checking rather than calling nqp::div_In 21:58
sleep& 21:59
Geth rakudo/ugexe/disable-default-curis: c43758f69b | (Nick Logan)++ | src/core.c/CompUnit/RepositoryRegistry.pm6
Allow default CURIs to be disabled

Previously there was no convenient way to disable the e.g. site, vendor, and core repositories. But when developing with application specific module install locations one might not want for modules to be used outside of that location. This add a new environment variables, RAKU_DISABLE_DEFAULT_CURIS, which can be set to anything to prevent the default repositories from being added to the repo chain itself. Note that it does still register those repositories with the registry.		 23:22
rakudo: ugexe++ created pull request #5338:
Allow default CURIs to be disabled		 23:24

Powered by Cro and the Raku® Programming Language.

Please report any issues / comments / feature requests as an issue on App::Raku::Log.

Thank you!