-
Notifications
You must be signed in to change notification settings - Fork 2
All issues
Issue creation is restricted in this repository
Issues
is:issue state:open
is:issue state:open
Search results
- Status: Open.#24 In ForthHub/fep-recognizer;
Rationale for
perceiveandperceptornamesnamingChoosing names, the artChoosing names, the artStatus: Open.#23 In ForthHub/fep-recognizer;API: token descriptors considered harmful
apiAn API method semantics considerationAn API method semantics considerationStatus: Open.#22 In ForthHub/fep-recognizer;Lifetime of qualified tokens
requrementRequirements to specifications or APIRequirements to specifications or APIStatus: Open.#21 In ForthHub/fep-recognizer;- Status: Open.#20 In ForthHub/fep-recognizer;
- Status: Open.#19 In ForthHub/fep-recognizer;
- Status: Open.#18 In ForthHub/fep-recognizer;
naming: methods to recognize various lexemes
apiAn API method semantics considerationAn API method semantics considerationnamingChoosing names, the artChoosing names, the artv4-reviewRelated to the proposal v4 by Matthias TruteRelated to the proposal v4 by Matthias TruteStatus: Open.#17 In ForthHub/fep-recognizer;API: interpretation and compilation semantics are enough for user-defined descriptors
apiAn API method semantics considerationAn API method semantics considerationStatus: Open.#16 In ForthHub/fep-recognizer;- Status: Open.#15 In ForthHub/fep-recognizer;
- Status: Open.#13 In ForthHub/fep-recognizer;
API: token component locations
apiAn API method semantics considerationAn API method semantics considerationv4-reviewRelated to the proposal v4 by Matthias TruteRelated to the proposal v4 by Matthias TruteStatus: Open.#11 In ForthHub/fep-recognizer;