Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Generalize or concretize ReachSet container types #695

Merged
merged 2 commits into from
Oct 13, 2019
Merged

Conversation

schillic
Copy link
Member

@schillic schillic commented Oct 7, 2019

Closes #690.

This PR solves the problem, but with an ugly hack.

The better way is to remove the type parameters of ReachSolution. This makes sense because the exact type is not known by an algorithm (because even if we know the set type, there are type parameters that we do not know in advance).
I did the first steps for that in #694, but it requires merging or removing the project methods of the CPost operators GLGM06 and TMJets. This is anyway reasonable now with the new projection based on individual ReachSets, but I did not have time for the change.

@schillic schillic requested a review from mforets October 7, 2019 19:35
@schillic
Copy link
Member Author

schillic commented Oct 8, 2019

Note that the "dev" build is green. So we would need to release a new version of LazySets first.

@schillic
Copy link
Member Author

This hack does not work anymore because of static arrays. Strange that it hit us so quickly, but it was a hack after all.

@schillic schillic merged commit fe950d7 into master Oct 13, 2019
@schillic schillic deleted the schillic/690 branch October 13, 2019 16:04
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Broken test convert error
2 participants