You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In order for type checking to work correctly, native aliases (and preferably not standard aliases) should make part of a NoSyn module's headers. If possible they should be hidden aliases, IE they work for the purposes of type checking, but attempting to use them in the file that imported them should fail. We would also want at some point for them to be imported at the programmers discretion using a scope modifier (similar to private/public in Java
The text was updated successfully, but these errors were encountered:
In order for type checking to work correctly, native aliases (and preferably not standard aliases) should make part of a NoSyn module's headers. If possible they should be hidden aliases, IE they work for the purposes of type checking, but attempting to use them in the file that imported them should fail. We would also want at some point for them to be imported at the programmers discretion using a scope modifier (similar to
private
/public
in JavaThe text was updated successfully, but these errors were encountered: