James
James
> because calling = on a key that doesn't exist will always return false for a value compare I think it's a bug, because we only see the error messages...
I added this design issue to work around the possibility of needing to do an IF_EXISTS AND IF_VALUE_IS sort of thing. Perhaps someone could have a look and comment on...
@jingyih > Regarding the idea of returning error when this happens, logically this is probably the right thing to do, but I think it is a pretty hard break on...
> Is this issue still active? and is there any plan to fix it? @csuzhangxc patches welcome I think.
@ItalyPaleAle, I think if TXN is to be used seriously, someone should just patch the operator... I'm too buried with other stuff, but would be happy to review your patch...
On Wed, Mar 3, 2021 at 7:20 AM Jean-Philippe Evrard wrote: > > What's the current reason of existence for errors.Wrapf? Was it only because of golang didn't support it...
@aequitas I was thinking about it, but don't know how to do this in the lexer. We'd have to agree on syntax first, and not copy puppet.
I find that avoiding thinking about what others does is a good way to think about design. Come up with a novel approach, and THEN compare after if necessary. Don't...