NopolResult should be created when calling build and not shared

[surli]

No description provided.

[monperrus]

@surli do you remember what you meant? could we close this one?

[surli]

In Nopol we should not use NopolResult as a field, it should be stateless regarding the result and create it only when calling build() method.

could we close this one?

No. It's not fixed yet.

[monperrus]

We pass the NopolContext to the constructor. Since, there is a one-to-one mapping between NopolContext and NopolResult, I don't see a problem here.

You can create as many Nopol objects as you need (until recently there was a problem with a static field currentStatement but this has been removed).