Don Inghram
Don Inghram
I should mention, this is ChaiScript 6.0.0
I think the real problem is that ChaiScript is assuming it can call a move operator on a non-R value, which destroys an object that is supposed to persist.
I guess what I am trying to say is that ChaiScript should not assume it can cast a non-R value to an R value.
Incidentally, I wish I knew this before I added it to our product. I don't want to have every 8==8 function call run through my object, but I don't know...
Sorry, my description of the problem sort of combines two issues. First: if I have an object that exposes an == operator and a conversion from int, every time 2...
OK, you are right. It is amazing how you can look at something for a while and think you are seeing one thing, but just be flat out wrong. So,...
Also, to fix the issue so that it doesn't have incorrect information in it, should I edit it and rewrite it, or update it with new notes that negate some...
FYI, making Binary_Operator_AST_Node::do_oper a static/public and using it inside Switch_AST_Node does fix the bug with comparing destroyed objects. Is this the fix you'd like to see in the pull request?...
Alternatively, I could make the parser create a Binary_Operator_AST_Node as the first child of the Case_AST_Node. Then, the optimizer would have the opportunity to change it to a Fold_Right_Binary_Operator_AST_Node. Then,...
Nevermind, I don't think we can create a Binary_Operator_AST_Node as the first child of the Case_AST_Node. This would require that we give it both the right and left hand sides...