-
-
Notifications
You must be signed in to change notification settings - Fork 50
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
There needs to be a features matrix for each backend #65
Comments
It depends on what you mean by "feature". All fundamental features of Lux are supported by all back-ends. If that weren't the case, the back-end wouldn't exist since it couldn't support the standard library, which is were Lux is truly embodied (more-so than the compilers themselves). With that said, there are some differences: These things are not fundamental to Lux, but they are notable differences. So, sure. |
Users who aren't totally familiar with each platform might not realize that Lux isn't going to implement a low latency parallel compacting GC for them ;) I'd maybe suggest: |
@jgarvin |
Not all features are supported on all backends. Most notably, I've seen Lua omitted in several places. There needs to be a features matrix that users can refer to to see what stdlib features are available to each backend.
The text was updated successfully, but these errors were encountered: