I've been a happy user of OPL language, which has lots of wonderful features. However, there is one remaining recurrent issue in data modeling, which prevents some intuitive modeling. This is called "cannot slice with nested constraints on subTuples".
|Who would benefit from this IDEA?||Any OPL user|
How should it work?
This has not been fixed over all recent releases and I think it prevents acceptance from new users. Also it makes life difficult even for experienced users like me, since we need workaround refactoring of the code, which makes the code more verbose and is a waste of time
|Priority Justification||Shows that IBM is still improving its legacy well adapted assets|
NOTICE TO EU RESIDENTS: per EU Data Protection Policy, if you wish to remove your personal information from the IBM ideas portal, please login to the ideas portal using your previously registered information then change your email to "email@example.com" and first name to "anonymous" and last name to "anonymous". This will ensure that IBM will not send any emails to you about all idea submissions