-
-
Notifications
You must be signed in to change notification settings - Fork 5.5k
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
Improved first-time experience #34614
Comments
Why do we need to collect issues? I think the separate issues are good enough. (1. #1255, 2. #10146, 3. https://github.com/JuliaLang/julia/issues?q=is%3Aopen+is%3Aissue+label%3Atestsystem, 4. multiple issues and was discussed at length before 1.0). |
The only issue that is not clear to me based on the many previous discussions is the What is the situation with |
The first two items are on my punch list of quality of life improvements. If you know anyone who has the skills and time to implement them, that would be helpful. There's been discussion of doing a quality of life release and maybe these will get more attention then. In the meantime, the same people who fix compiler bugs, performance issues, scope gripes, and fight compile time latency are the same people who would be implementing these features. Regarding 3, overhauling the Removal of |
The base language could provide simple constructs to improve the first-time experience:
undef
keyword inMatrix{Float64}(undef, 3, 3)
I am advising a student who struggled with the
undef
business that we are used to as more experienced users. He also missed theimport VeryLongModuleName as VLMN
syntax that is quite natural for people coming from Python. Would it be possible to consider these improvements in next major releases? I understand that some of these issues are already being tracked on GitHub, but I couldn't find a single issue collecting them.The text was updated successfully, but these errors were encountered: