| Subject: | Depreciation way of work in LMU |
For several reasons it's required for users of LMU to make a decision about the behavior to use.
In general - there're two general behaviors:
1) Precise: Functions return a dedicated state when no result is available (eg. undef in the example of "all" - when no item was given).
2) Unprecise: return some kind of default value (probably choosable?)
Additional implementations might contain functions which clash with other utility packages - thus allowing pick the list of implementations / behaviors or whatever is intended.
The other option: break behavior immediately has been discussed and is not available for next release version.