Skip to content

Strict references to SystemCallError and Errno in C#5793

Closed
dearblue wants to merge 1 commit into
mruby:masterfrom
dearblue:strict-errno
Closed

Strict references to SystemCallError and Errno in C#5793
dearblue wants to merge 1 commit into
mruby:masterfrom
dearblue:strict-errno

Conversation

@dearblue
Copy link
Copy Markdown
Contributor

For example, if SystemCallError is changed, it may invite undesirable behavior.

% bin/mruby -e '
E = SystemCallError
SystemCallError = String
E._sys_fail(1)
'
-e:4: allocation failure of String (TypeError)

For example, if `SystemCallError` is changed, it may invite undesirable behavior.

```console
% bin/mruby -e '
E = SystemCallError
SystemCallError = String
E._sys_fail(1)
'
-e:4: allocation failure of String (TypeError)
```
@dearblue dearblue requested a review from matz as a code owner September 17, 2022 13:21
@matz
Copy link
Copy Markdown
Member

matz commented Sep 17, 2022

Hmm, it's users fault to see the failure when they redefine class names (if we don't see fatal failures).
All we have to do is improving errors to be more comprehensive, probably.

@matz matz closed this in db536da Sep 17, 2022
@dearblue
Copy link
Copy Markdown
Contributor Author

Indeed it is. Thanks for reviewing it.

@dearblue dearblue deleted the strict-errno branch September 18, 2022 02:27
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.

2 participants