Stack Switching Ontology
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 5/5
- Tiempo estimado
- Más de una semana
- Aptitud para principiantes
- 25/100
- Tipo de issue
- Documentación
- Claridad
- Necesita aclaración
- Estado de actividad
- Estancado
- Stack tecnológico
- wasm
- Área
- compilers
Línea de trabajo
Start by reading the issue's proposed definitions and the surrounding stack-switching proposal context. Review whether the terms cover the concepts needed for the design process and identify any ambiguities or missing terminology. Done means the project has an agreed, useful terminology set rather than an implementation change.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
It can be difficult to discuss different aspects of stack switching without some form of common terms for different aspects.
This note is an attempt to support the design process by defining some concepts. There is a strong possibilitycertainty that new terms not mentioned here will be needed; so this should be viewed as the start of a conversation.
These definitions are listed in alphabetical order, for lack of other organizing principles.
- Delimiter Label
A delimiter label is a term that denotes a prompt bracket. Delimiter labels may or may not be values. - Opt-in
Opt-in refers to a systemic property where a given feature (in this case stack switching generally) is only available after some positive action on the part of a computation. - Prompt Bracket
A prompt bracket marks the beginning of a suspend-able computation. - Reified Continuation
A reified continuation is a value that denotes the remaining computation of a task after it has suspended. - Response Computation
The computation that is launched as a result of suspending a task. - Resume Point
A resume point marks where a suspended computation is resumed. - Safety
Safety refers to a verifiable property of computations that certain events cannot occur. For example, in the case of a resume point, the primary safety requirements include that any data values transmitted meet declared types and that the computation being resumed was suspended. - Suspension Bracket
A suspension bracket marks the point where a computation has suspended. Immediately after the suspension bracket is the computation that is responding to the suspension. - Task
A complete suspendable computation, starting from when the task is initiated -- marked by a prompt bracket -- and ending when the computation terminates finally. A task may suspend and be resumed multiple times between the initial creation and the final termination.
Note that these terms should not be viewed as prejudicing any particular design approach.
- Lenguaje dominante
- WebAssembly
- Estrellas
- 216
- Forks
- 19
- Métricas de merge de PR
- Sin PR fusionados en 30 d
Preparar el entorno
- Sin Dockerfile ni archivo de Docker Compose
- Sin plantilla de pull request
- Leer la guía de contribución
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/stack-switching
-
Dificultad 5/5 Más de una semana Aptitud para principiantes 35/100
WebAssembly/stack-switching#156 · 1 comentario ·
-
Should `cont.new` be constant?Abierto
Dificultad 5/5 Más de una semana Aptitud para principiantes 35/100
WebAssembly/stack-switching#145 · 4 comentarios ·
-
Use `typeuse` in text format?Abierto
Dificultad 5/5 Más de una semana Aptitud para principiantes 35/100
WebAssembly/stack-switching#144 · 4 comentarios ·
-
JSPI integrationAbierto
Dificultad 5/5 Más de una semana Aptitud para principiantes 25/100
WebAssembly/stack-switching#131 ·
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 45/100
WebAssembly/stack-switching#128 · 6 comentarios ·
Todos los issues de WebAssembly/stack-switching
Issues similares
-
bug engine spec compliance
Dificultad 2/5 1-3 horas Aptitud para principiantes 84/100
frostney/GocciaScript#1402 ·
Los mantenedores suelen responder en 1 día
-
bug needs triage
Dificultad 2/5 1-3 horas Aptitud para principiantes 85/100
Los mantenedores suelen responder en 1 día
-
After `require "openssl"`, a top-level `Digest` is `OpenSSL::Digest`, not the `Digest` moduleAbierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 88/100
Los mantenedores suelen responder en 1 día
-
Dificultad 1/5 Menos de una hora Aptitud para principiantes 88/100
yhirose/cpp-peglib#344 ·
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
Los mantenedores suelen responder en 1 día