Built-in priority for expression trees?

I cannot find a built-in .NET FCL precedence concept to use when building Expression Trees . Ref Namespace System.Linq.Expressions . Is it something that needs to be handled manually in the code, or is it somehow implicit and I don't recognize it, maybe via helper methods or classes?

I want to apply it to math operations to provide 3 + 5 * 10 results in 53 instead of 80.

+2


a source to share


1 answer


The whole point of representing code as a tree is that the priority is encoded in the tree structure itself, so you don't need to worry about that.



+1


a source







All Articles