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

modelize: broken mproperties can have definitions #2602

Closed
wants to merge 1 commit into from

Conversation

privat
Copy link
Member

@privat privat commented Dec 21, 2017

so, when keep-going is activated, mproperty.intro and other related services wont crashes.
Thus fixes #2599
moreover, the mpropdefs attempts are registered in the model (if one need them?).

This might however add some unexpected effects (one does not simply add broken entities into mordor^Wmodel).

TODO: the same thing with classes?

so, when keep-going is activated, mproperty.intro and other related services wont crashes.
Thus fixes nitlang#2599
moreover, the mpropdefs attempts are registered in the model (if one need them?).

This might however add some unexpected effects (one does not simply add broken entities into mordor^Wmodel).

TODO: the same thing with classes?

Signed-off-by: Jean Privat <[email protected]>
@privat
Copy link
Member Author

privat commented Mar 2, 2018

test this please

2 similar comments
@privat
Copy link
Member Author

privat commented May 31, 2018

test this please

@privat
Copy link
Member Author

privat commented May 31, 2018

test this please

@Morriar
Copy link
Member

Morriar commented Jul 15, 2019

That's one of the problem with is_borken, you never know what you can do with them before an assert fails.

Exceptions could be useful here!

@privat privat closed this Aug 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

bug: _intro not initialized when using --keep-going option
2 participants