Suggestion: use PEP-like process for changes

paulmelis
Wed, 23 Jun 2021 16:14:44 +0000
Internals & Design

Implicitly loaded modules in the future?

Sorry for interfere, but this thread is so long and there was so many ideas, that is really hard to understand what features are proposed.

Can you give an example, how code is going to look like with proposed features? Small MWE, just to understand what we are talking about and how it differs from the current system.

Meta-point in response this remark by @skoffer (with which I agree): with other languages, say Python and Go, more structured processes to discuss possible language evolution and improvements have been put in place over the years, e.g. Python’s PEPs. As probably is known by the Julia devs, each Python PEP lists a single proposed change, including rationale, discussion on pros and cons, implementation strategy, etc. This might be a model that can be of interest to Julia development at some point (perhaps still too early) to have more structured discussions and ways to get feedback on a clear proposal. It would also force those proposing changes to come up with a more concrete outline, which can be debated more sharply. A light-weight start could be to have a forum thread per proposal in a separate part of this discourse, which is moderated to make sure it stays on topic.

38 posts - 15 participants