| releasable6 | Next release in ≈1 day and ≈15 hours. There are no known blockers. Please log your changes in the ChangeLog: github.com/rakudo/rakudo/wiki/ChangeLog-Draft | 03:00 | |
|
04:05
lue joined
04:06
ShimmerFairy left
04:19
lue is now known as ShimmerFairy
|
|||
| ab5tract | I'm confused about lazy list handling in feed operators | 09:48 | |
| As far as I can tell, there is no way to create a call that takes a single element. But that seems to be a necessary feature for handling lazy lists? | |||
| m: [1,2,3].roll(*) ==> say() | 09:49 | ||
| camelia | (...) | ||
| ab5tract | m: [1,2,3].roll(*) ==> { $_ + 5 }() ==> dd() | 09:50 | |
| camelia | Failure.new(exception => X::Cannot::Lazy.new(action => ".elems", what => "")) | ||
| ab5tract | m: [1,2,3].roll(*) ==> { $_.map: * + 5 }() ==> dd() | ||
| camelia | (7, 6, 6, 8, 6, 6, 8, 6, 8, 8, 7, 8, 8, 7, 8, 7, 6, 7, 7, 8, 7, 6, 7, 8, 8, 7, 6, 8, 8, 6, 6, 8, 6, 8, 6, 7, 6, 7, 7, 7, 7, 7, 7, 6, 6, 7, 7, 7, 7, 8, 8, 6, 7, 6, 8, 8, 7, 6, 8, 7, 7, 7, 8, 6, 7, 6, 6, 8, 7, 6, 6, 6, 8, 6, 6, 8, 8, 7, 6, 6, 7, 7, 8, 8… | ||
| ab5tract | I don't see any great utility in feed operators if you still have to call map? | 09:52 | |
| Well nevermind, my main concern was that objects implementing .append can't be combined, but it looks like I was doing a dumb by using for instead of .map | 09:55 | ||
| timo | m: [1,2,3].roll(*) ==> map { $_ + 5 } ==> dd() | 09:58 | |
| camelia | (7, 8, 7, 8, 6, 8, 6, 6, 7, 8, 7, 6, 7, 8, 8, 8, 6, 6, 8, 6, 6, 7, 6, 6, 6, 8, 6, 8, 7, 8, 7, 8, 6, 7, 8, 8, 6, 7, 6, 8, 7, 7, 6, 8, 8, 6, 8, 7, 8, 7, 7, 6, 6, 8, 8, 8, 7, 7, 6, 6, 7, 8, 8, 6, 7, 6, 6, 6, 6, 8, 7, 7, 8, 6, 7, 6, 6, 8, 7, 8, 6, 8, 8, 8… | ||
| ab5tract | Here's a gist that demonstrates some of my struggle with feeds | 11:41 | |
| An aside, but still about feeds.. I'm wondering whether we could ever allow Callables instead of Calls for the pipeline expressions | 11:42 | ||
| (gist: gist.github.com/ab5tract/954fe3b45...6892197c9) | 11:43 | ||
|
12:49
finanalyst joined
|
|||
| [Coke] | Any more commits expected before release? | 13:06 | |
| might cut the release branch later today | 13:20 | ||
| lizmat is not planning any | 13:22 | ||
| m: class A { q/has $.foo/.EVAL }; BEGIN dd A.^attributes>>.name; dd A.^attributes>>.name | 13:59 | ||
| camelia | () ("\$!foo",) |
||
| lizmat | this implies that you can add attributes at runtime? | ||
| I wonder whether this is a bug or a feature | 14:00 | ||
|
14:06
finanalyst left
|
|||
| timo | the attribute will have a hard time working without calling compose on the type afterwards, right? | 14:13 | |
| lizmat | m: class A { q/has $.foo = 42/.EVAL }; dd A.new | 14:17 | |
| camelia | P6opaque: no such attribute '$!foo' on type A in a A when trying to get a value in block <unit> at <tmp> line 1 |
||
| lizmat | m: class A { BEGIN q/has $.foo = 42/.EVAL }; dd A.new | ||
| camelia | A.new(foo => 42) | ||
| lizmat | so only if the outer compunit is still compiling, could we consider allowing this | 14:18 | |
|
14:19
shareable6 left
14:21
shareable6 joined
16:31
librasteve_ left
16:33
finanalyst joined
|
|||
| lizmat just added a new alias: alias rut='(){ RAKUDO_RAKUAST=1 raku -e "$1; CHECK dd" }' | 17:05 | ||
| which will show the RakuAST tree for the given Raku code: rut 'say "foo" | |||
|
17:39
librasteve_ joined
19:23
lue joined
19:26
ShimmerFairy left
19:49
librasteve_ left
|
|||
| releasable6 | Next release in ≈19 hours. There are no known blockers. Please log your changes in the ChangeLog: github.com/rakudo/rakudo/wiki/ChangeLog-Draft | 23:00 | |
| [Coke] | releasable6: next | ||
| releasable6 | [Coke], Next release in ≈19 hours. There are no known blockers. 43 out of 45 commits logged | ||
| [Coke], Details: gist.github.com/782ecc905f2b3d2b96...5ddb0ae42b | |||
| lizmat | m: dd one(Any).defined | 23:34 | |
| camelia | Bool::True | ||