Process requirement for sufficient demand
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 5/5
- Tiempo estimado
- Más de una semana
- Aptitud para principiantes
- 20/100
- Tipo de issue
- Nueva funcionalidad
- Claridad
- Bastante claro
- Estado de actividad
- Estancado
- Área
- developer-experience
Línea de trabajo
Comienza con issue #68 y lee el hilo completo de comentarios, incluida la propuesta editada y el debate sobre los requisitos de Stage 3. Se considera completado llegar a una decisión y dejar constancia de ella sobre si cada funcionalidad de Stage 3 debería requerir una demanda sustancial de la base de usuarios; el payload no especifica archivos ni pruebas que ejecutar.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
WebAssembly has a significant backwards compatibility constraint. It is also exploring an almost entirely new space and solving very hard problems requiring substantial design and implementation work. As such, it is important to make sure that any designs developed, implemented, and shipped have been substantially evaluated on whether they achieve their intended purpose. To this end, I suggest the following amendment to the process:
As a requirement for advancing to Stage 3, every feature of the proposal should have approval from a substantial user base (where the appropriate scale/meaning of "substantial" and "user base" depends on the specifics of the proposal).
There are two primary reasons for this revision:
- We cannot evaluate whether the proposal's design for a feature effectively achieves its intended goal without a substantial user base to either demonstrate its utility or to provide feedback on how the proposal needs to be revised to meet their needs.
- As much of that evaluation should be done prior to implementation to reduce churn due to design changes.
With this requirement in place, when the reference types proposal went to Stage 3 we would have seen that, although external references had a big user base, subtyping did not and so should be carved out into a separate proposal. Furthermore, this separation would have made it apparent that many other proposals do not need to depend on the reference types proposal. Many uses of type imports do not need any constraints at all (arguably external references are an example of this), and alternative (even more expressive) constraints besides subtyping could be explored. Although exception handling uses exnref, which might represent uninterpretable exceptions depending on the host, there is no requirement that exnref be related to external references. Even garbage collection does not depend on anyref or external references; we demonstrated that even languages relying on a uniform representation would generally prefer to use a uniform representation that is specialized to the needs of the language over a useless type like anyref. So the separation this requirement would have encouraged would have also reduced the dependencies between proposals.
But pulling back from the current situation, what do y'all think of the proposed revision that every feature of a Stage 3 proposal should have enough demand to warrant implementation and to enable proper evaluation?
[This was substantially edited thanks to feedback from @jgravelle-google.]
- Lenguaje dominante
- Python
- Estrellas
- 1.1k
- Forks
- 78
- Métricas de merge de PR
- Sin PR fusionados en 30 d
Preparar el entorno
Este proyecto no incluye contenedor de desarrollo, Dockerfile ni guía de contribución, así que la configuración corre por tu cuenta: empieza por su README y consulta nuestra guía para la primera contribución para los pasos generales.
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de WebAssembly/proposals
-
Dificultad 5/5 Más de una semana Aptitud para principiantes 35/100
WebAssembly/proposals#243 · 5 comentarios · 4 reacciones ·
-
Dificultad 5/5 Más de una semana Aptitud para principiantes 20/100
WebAssembly/proposals#175 · 2 comentarios ·
-
"inline" finished proposals?Abiertogood first issue help wanted
Dificultad 2/5 1-3 horas Aptitud para principiantes 45/100
WebAssembly/proposals#99 · 9 reacciones ·
-
Prevent conflicting opcodesAbierto
Dificultad 5/5 Más de una semana Aptitud para principiantes 25/100
WebAssembly/proposals#148 ·
-
Dificultad 5/5 Más de una semana Aptitud para principiantes 25/100
WebAssembly/proposals#21 · 13 comentarios · 14 reacciones ·
Todos los issues de WebAssembly/proposals
Issues similares
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 77/100
mozilla-ai/cq#601 ·
Los mantenedores suelen responder en 1 día
-
Bump Python to 3.14 or 3.15Abierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 68/100
Los mantenedores suelen responder en 1 día
-
intcomma returns exponential notation for large floatsPosiblemente ocupada @Omarinho12345 la tomó hoy. Abierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
python-humanize/humanize#521 ·
Los mantenedores suelen responder en 1 día
-
LUCJ pass manager raises NoEdgeBetweenNodes when an edge is bad for two two-qubit gatesPosiblemente ocupada @hat-im la tomó hoy. Abierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 76/100
Los mantenedores suelen responder en 1 día
-
opensubtitlescom: provider rejects pt-PT even though its own converter maps itPosiblemente ocupada @paulo-0308 la tomó hoy. Abierto
Dificultad 1/5 Menos de una hora Aptitud para principiantes 88/100
Diaoul/subliminal#1405 ·