[#70252] Re: [ruby-cvs:58640] nobu:r51492 (trunk): node.c: NODE_ALLOCA for ALLOCV — Eric Wong <normalperson@...>
Besides possible backwards compatibility, can we drop volatile
3 messages
2015/08/05
[#70257] [Ruby trunk - Feature #11420] [Open] Introduce ID key table into MRI — ko1@...
Issue #11420 has been reported by Koichi Sasada.
11 messages
2015/08/06
[#70337] Re: [Ruby trunk - Feature #11420] [Open] Introduce ID key table into MRI
— Eric Wong <normalperson@...>
2015/08/11
Nice. Thank you guys for looking into this.
[#70349] Re: [Ruby trunk - Feature #11420] [Open] Introduce ID key table into MRI
— Eric Wong <normalperson@...>
2015/08/12
Btw, did you consider using flexible array to avoid extra malloc
[#70355] Re: [Ruby trunk - Feature #11420] [Open] Introduce ID key table into MRI
— Юрий Соколов <funny.falcon@...>
2015/08/12
I thought to suggest to embed hash_id_table directly into places when it is
[#70356] Re: [Ruby trunk - Feature #11420] [Open] Introduce ID key table into MRI
— SASADA Koichi <ko1@...>
2015/08/12
On 2015/08/13 4:29, Юрий Соколов wrote:
[#70358] Re: [Ruby trunk - Feature #11420] [Open] Introduce ID key table into MRI
— Eric Wong <normalperson@...>
2015/08/12
SASADA Koichi <ko1@atdot.net> wrote:
[#70509] [Ruby trunk - Misc #11276] [RFC] compile.c: convert to use ccan/list — ko1@...
Issue #11276 has been updated by Koichi Sasada.
3 messages
2015/08/21
[#70639] the undefined behavior of an iterator if it is modified inside of the block to which it yields — Daniel Doubrovkine <dblock@...>
(this is my first time e-mailing list list, so apologies for any misstep :)
4 messages
2015/08/31
[ruby-core:70600] [Ruby trunk - Feature #8437] custom operators, unicode
From:
duerst@...
Date:
2015-08-27 04:36:39 UTC
List:
ruby-core #70600
Issue #8437 has been updated by Martin D=C3=BCrst. Matthew Kerwin wrote: > Neither for nor against this idea at the moment, Same here. > but which "math operator plane" do you mean? A quick read on wikipedia (= ((<link|URL:http://en.wikipedia.org/wiki/Mathematical_operators_and_symbols= _in_Unicode>))) lists the following potential Unicode 6 blocks: [shortened] The right way to do this is not by using blocks, but by using character pro= perties. Unicode General Category (see http://www.unicode.org/reports/tr44/= #General_Category_Values) would provide a starting point. ---------------------------------------- Feature #8437: custom operators, unicode https://bugs.ruby-lang.org/issues/8437#change-54008 * Author: Eike Dierks * Status: Open * Priority: Normal * Assignee:=20 ---------------------------------------- The ruby language does currently one support a predefined set of operators. It would be nice to add custom operators. A lot of people ask about the elvis operator aka (?:) to cope with nil, aka= rails try() This probably is a problem with the parser at first, because introducing new operators makes parsing a lot more complicated. Maybe we could allow symbols from the unicode space to be used as new operators? That would be compatible with all before code written in ascii. So we could allow all the symbols from the unicode Math operators plane to be available as operators in Ruby. While few of you might have tried that, Unicode is fully available for naming identifiers. We should also extend the set of operators to the unicode space. While we are still not used to it now, to have some unicode characters in our codes, could really add to the expressivness. So as of today, you can already name your variable like delta_t or =CE=94t Or if you're working with angles, you might call your variables =CE=B1 or =CE=98 This is completely legal in Ruby. I'm asking for: this_set =E2=88=AA other_set or maybe we could even do this for prefix like: =E2=88=9A2 I'd believe the math operator plane of unicode should be removed from the allowable names of identifiers, but should instead be reserved for operators in the parser, like + nowdays = is. --=20 https://bugs.ruby-lang.org/