3 ms·
I've seen some complaints about this, but the existence of Texas versions of the operators makes this absolutely fine in my eyes. I don't see why people would
by hahainternet 11y ago
I've seen some complaints about this, but the existence of Texas versions of the operators makes this absolutely fine in my eyes.
I don't see why people would begrudge the ability to use the 'proper' mathematical symbols just because they're slightly harder to type.
Of course, it's another situation where Perl 6 is just crazy, but crazy awesome :)
- mbrock 11y agoI instinctively feel like I'm going to run into some stupid problems, but I blame that on the extreme difficulty in 2015 of getting UTF-8 to work consistently with the mess of locale variables, terminal emulator configuration, vty multiplexers, editors, source control systems, MIME types, and who knows what. Pretty much every time I've put Unicode symbols in source code I've ended up regretting it later for some frustrating reason. There are always solutions though... and kudos to Perl 6 for giving it a shot.
- hahainternet 11y agoI'm sure you're right, the REPL uses Linenoise which is single byte character only for example. The only way to fix these problems though is to increase their use, so ultimately the end goal will be worth it. That seems to have been the Perl 6 mantra for a decade or so.
- zengargoyle 11y agoTip: don't install Linenoise and use rlwrap instead. You get unicode, history across sessions, and if you tweak it right tab completion.
- bshimmin 11y agoFor anyone confused by "Texas versions", this might help: http://design.perl6.org/S99.html#Texas_operator http://design.perl6.org/S99.html#Texas_operator
- hahainternet 11y agoMy apologies, I didn't notice that it wasn't explicitly mentioned on the input page.