|
6macros: discussing the finer points of Perl 6 macros, Qtrees, and how to stay sane | irclog: irclog.perlgeek.de/6macros/today Set by moderator on 17 June 2015. |
|||
|
01:48
ilbot3 joined
|
|||
| moderator | 6macros: discussing the finer points of Perl 6 macros, Qtrees, and how to stay sane | irclog: irclog.perlgeek.de/6macros/today | ||
|
11:15
Ven joined
12:24
Ven joined
|
|||
| Ven | I keep constantly wishing instantiation time and compile-time weren't different :) | 12:25 | |
| (or "so different") | |||
| obviously, there's some friction due to what can be computed at compile-time | |||
| But I know I find myself wishing often to be able to write stuff like | |||
| role Something[::T] { method create of T { T.new } } | 12:26 | ||
| but that most probably will never work | |||
|
12:53
Ven joined
14:21
Ven joined
|
|||
| masak | insight of the day, propelled forward by tinkering with 007: | 19:25 | |
| in a langiage like Perl 6 where "custom op" merely means that the op symbol has been bound in user-space, it doesn't make a whole lot of sense to single out custom ops as a separate Qtree type. | 19:26 | ||
| or rather, it all becomes a sliding scale: was it defined in the compiler itself, in the/a setting, in a loaded module, or in a script? | |||
| putting the focus on some of these latter things as "custom" misses the important point, that no matter where it was defined, it's treated in a very first-class manner by the whole language. | 19:28 | ||
| "custom" only makes sense in a language that treats those custom things as second-class citizens. | 19:31 | ||
|
20:37
vendethiel- joined
21:14
Quom joined
21:38
masak_ joined
|
|||
| vendethiel- waves | 23:42 | ||
| you're probably asleep, though, masak | |||
| [00:13] <masak> 'night, #perl6 | 23:43 | ||
| indeed! | |||
| I think what you say goes in the way of the "applying operators is just like calling sub" thing I said a few times earlier | 23:49 | ||