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

Fix issue #2859 (fatal() without checking if errors are gagged) #2860

Merged
merged 3 commits into from Sep 29, 2018

Conversation

kinke
Copy link
Member

@kinke kinke commented Sep 28, 2018

No description provided.

@kinke
Copy link
Member Author

kinke commented Sep 28, 2018

Well I'd better check what unknown kind of AddrExp this is.

Edit: TOKdotvar.

@kinke kinke changed the title Fix issue #2859 (fatal() without checking if errors are gagged) WIP: Fix issue #2859 (fatal() without checking if errors are gagged) Sep 28, 2018
@kinke kinke changed the title WIP: Fix issue #2859 (fatal() without checking if errors are gagged) Fix issue #2859 (fatal() without checking if errors are gagged) Sep 28, 2018
… gagged)

It was the only unguarded fatal() call in that file.
[To be squashed.]

I assume a DotVar expression making it here implies its address is not
constant.
@kinke kinke merged commit 7e9db71 into ldc-developers:master Sep 29, 2018
@kinke kinke deleted the fix2859 branch September 29, 2018 15:29
@kinke
Copy link
Member Author

kinke commented Sep 29, 2018

Merged eagerly as an unreachable is clearly better than a (potentially) gagged error + fatal().

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.

None yet

1 participant