Prevent unnesting whenever possible without BDDs

[Broes De Cat]

When not using bdds, unnesting known functions (either builtin or given) is useless, as this is only using for query optimization (for which we need bdds). On the other hand, it is important to prevent it, because it strongly increases grounding time (*|introduced domain|). Should be easy to add to unnesting transformations.

[Stef De Pooter]

Resolved by commit b3168f8dad72.

[Bart Bogaerts]

The way it is fixed now, is not the right way. Now, one checks just for the GROUNDWITHBOUNDS option to be true when one decides whether or not to unnest.

The right way is using two different transformations:

• One transformation never unnests known terms,
• One transformation always unnests them (to be used when constructing bdds)

Because for example, we might want to manipulate bdds when groundwithbounds is disabled, or we still want to be able to do the first unnesting in the grounding, even when we ground with bounds...

[Bart Bogaerts]

see #82: fixed now?

→ 4d38c4462ea9

[Broes De Cat]

Removing milestone: Second Release (automated comment)