Carlo Zancanaro on Nostr: nprofile1q…3s5e3 With an appropriately parameterised parser you could reuse the ...
nprofile1qy2hwumn8ghj7un9d3shjtnddaehgu3wwp6kyqpqmcptsh7w87wfwx94kd65xpkr470m84smz3hwujxkcmfvgqnc2nusq3s5e3 (nprofile…s5e3) With an appropriately parameterised parser you could reuse the parser and load different operators into it. It is more complex, though, so I'm not really recommending it. I'm more curious about how convenient it could be. I guess it would just be a fancy parser generator over a token stream, which is a well worn path.
I don't fully understand what you mean about having the same semantic. For instance, Ruby uses the comma to separate arguments, whether they are positional, keyword, or block. These have (slightly) different semantics, but they all use the same separator.
I don't fully understand what you mean about having the same semantic. For instance, Ruby uses the comma to separate arguments, whether they are positional, keyword, or block. These have (slightly) different semantics, but they all use the same separator.