|
00:27
hankache_ joined
00:31
hankache left
01:49
rakkable left
02:02
lizmat left
02:05
rakkable joined
02:23
lizmat joined
05:08
vrurg joined
05:09
vrurg_ left
06:39
hankache_ left
08:01
nine_ left,
nine joined
|
|||
| Geth | rakudo/lizmat-82: 2bad874309 | (Elizabeth Mattijsen)++ | src/Raku/ast/literals.rakumod RakuAST: if "&val" is not resolved, don't bother doing a call Before this commit a dummy Callable was being inserted to mimic val() processing. There's no need for that, as that Callable just returned the value as is. Instead just call the val() processor if it is available. Practically this will only affect core setting compilation before val() processing as becomes active. Still felt this was needed for code clarity. |
10:31 | |
| rakudo: lizmat++ created pull request #6861: RakuAST: if "&val" is not resolved, don't bother doing a call |
|||
| rakudo/lizmat-83: 1f5d3c77df | (Elizabeth Mattijsen)++ | src/core.c/allomorphs.rakumod Remove return statement from "parse_win" in val processing Since all of the choices in "parse_win" contained either a return or a die statement, and "parse_win" was in one case called at the end of the val() sub, it felt like a good idea to remove the return statements from the "parse_win" Callable, and add a return statement to the one case where "parse_win" needed it. |
11:08 | ||
| rakudo: lizmat++ created pull request #6862: Remove return statement from "parse_win" in val processing |
|||
|
11:12
samebchase joined,
samebchase left
|
|||
| Geth | rakudo/lizmat-84: 1be1db5141 | (Elizabeth Mattijsen)++ | src/core.c/allomorphs.rakumod Remove GUARDED-NUMERIC implementation-detail sub It was only called in one place, and the code was minimal, so just move the code to where it was being called |
11:19 | |
|
11:33
samebchase joined
|
|||
| Geth | rakudo/lizmat-85: 7310615851 | (Elizabeth Mattijsen)++ | 20 files RakuAST; make .get-implicit-lookups return an nqp::list Rather than a HLL list. Since all calls to .get-implicit-lookups were wrapped in a self.IMPL-UNWRAP-LIST, and .get-implicit-lookups always wrapped any NQP list in a self.IMPL-WRAP-LIST, it doesn't make any sense to do this. So remove the IMPL-WRAP-LIST from .get-implicit-lookups, and remove all IMPL-UNWRAP-LIST from calls to .get-implicit-lookups. This method is getting called more than 100K times during setting compilation. |
12:04 | |
| rakudo: lizmat++ created pull request #6863: Remove GUARDED-NUMERIC implementation-detail sub |
12:05 | ||
| rakudo: lizmat++ created pull request #6864: RakuAST; make .get-implicit-lookups return an nqp::list |
|||
|
12:35
lizmat left
13:05
ShimmerFairy left
13:22
lizmat joined
13:35
ShimmerFairy joined
13:42
Pixi left,
coleman left,
kjp left,
djinni` left
13:49
Pixi joined,
coleman joined,
kjp joined,
djinni` joined
|
|||
| Geth | rakudo/lizmat-86: 2773abb581 | (Elizabeth Mattijsen)++ | src/Raku/ast/literals.rakumod RakuAST: inline ::QuotedString.IMPL-CHECK-PROCESSORS It was only called in one place. Also only do processor checking only if there are any processors to check |
14:15 | |
| rakudo: lizmat++ created pull request #6865: RakuAST: inline ::QuotedString.IMPL-CHECK-PROCESSORS |
14:16 | ||
|
14:37
ShimmerFairy left
14:39
ShimmerFairy joined
|
|||
| Geth | rakudo/lizmat-87: 46e8a0d99b | (Elizabeth Mattijsen)++ | src/Raku/ast/literals.rakumod RakuAST: simplify ::QuotedString.IMPL-NATIVE-LITERAL-KIND Checking for processors can be done in a single if. Use the same logic as the "ast-type" method which follows |
14:48 | |
| rakudo: lizmat++ created pull request #6866: RakuAST: simplify ::QuotedString.IMPL-NATIVE-LITERAL-KIND |
|||
|
14:49
finanalyst joined
|
|||
| [Coke] returns (off line yesterday for volunteer reasons, then network issues, then exhaustion. :) | 14:59 | ||
| lizmat | [Coke]: welcome back | ||
| [Coke] | j | 15:03 | |
| Geth | rakudo/lizmat-88: e62cc8e44e | (Elizabeth Mattijsen)++ | 2 files RakuAST: access val() processing in an easier way By adding a val() candidate taking a native string, and then not bothering HLLization in ::QuoteString.IMPL-PROCESS-PART |
15:13 | |
| rakudo: lizmat++ created pull request #6867: RakuAST: access val() processing in an easier way |
15:14 | ||
|
15:40
ilogger2 left
15:48
ShimmerFairy left
15:50
ilogger2 joined,
ShimmerFairy joined
16:16
vrurg_ joined
16:18
vrurg left
|
|||
| Geth | rakudo/lizmat-89: 5a655d5bf3 | (Elizabeth Mattijsen)++ | src/Raku/ast/literals.rakumod RakuAST: re-image ::QuotedString.IMPL-EXPR-QAST Instigated by github.com/rakudo/rakudo/issues/6860 the problem was that it was assumed that concatenation of interpolated strings could be done with nqp::ops such as concat and join. However, that means that any additional candidates to infix:<~> ... (6 more lines) |
17:00 | |
| rakudo: lizmat++ created pull request #6868: RakuAST: re-image ::QuotedString.IMPL-EXPR-QAST |
|||
| rakudo/main: 0138d1dd6f | (Elizabeth Mattijsen)++ (committed using GitHub Web editor) | 12 files RakuAST: native int variables don't need := 0 initialization (#6835) * RakuAST: native int variables don't need := 0 initialization Native int variables are "born" with the value 0. This removes this unnecessary initialization from many lexical variables, and also changes some variables to native ints as they're clearly intended to be used as flags. * Oops, forgot one "int" |
18:31 | ||
| rakudo/lizmat-90: 41e8b3ccf8 | (Elizabeth Mattijsen)++ | src/Raku/ast/var-lowering.rakumod RakuAST: streamline ::IMPL::VarLoweringFrame.IMPL-WALK - remove unnecessary variable - merge 2 if structures - rewrite without needing return |
19:35 | ||
| rakudo: lizmat++ created pull request #6870: RakuAST: streamline ::IMPL::VarLoweringFrame.IMPL-WALK |
19:36 | ||
|
20:05
lizmat left,
lizmat_ joined
20:36
hankache_ joined
21:30
hankache_ left
21:31
hankache joined
21:51
lizmat_ left
21:52
lizmat joined
21:57
hankache left,
finanalyst left
|
|||