Should append null fail, append BLANK! add nothing unless /ONLY?
Variadic Return Values (not VARARGS! return values...)
Enfix Normal Revisited: Unlimited Default, One-Eval Operator?
Special Syntax for FOR-EACH/etc. to receive ACTION!s?
BLANK!-in, NULL-out convention vs. LOGIC!-returning actions
Why VOID! is not like UNSET! (and why it's "more ornery")
Should TRAP and CATCH return null if no fails/throws?
Facing the facts: SWITCH must evaluate clauses
Evaluating the worthiness of VALUE_FLAG_UNEVALUATED
VOID! (and the end of "blankification")
(not) Bringing Blankification Back
Limiting PRINT to BLOCK!, TEXT! (perhaps BLANK! to opt-out?)
Re-imagining DO/NEXT (now called EVALUATE)
The Coming of User-Defined Types
Deepening the Lake: / as zero-length PATH!
Letting Go of Enfix Path Dreams (but fixing it with "Magic")
Issues with "Invisibles": a truly disappearing COMMENT
Key Question on Virtual Binding and Mutability
ASSERT vs. [end]able FAIL
What happens to FUNCTION! arguments and locals when the call ends?
Should we kill off defaults-in-function-specs via GROUP!
Should refinement arguments be REFINEMENT! if used?
Strict Equality, Lax Equality, Equivalence, Sameness: IS and =
Stopping the /INTO Virus
The fallout from the SWITCH fallout feature
The Case for Literal (or soft-quoted?) branches in CASE
Should function arguments to functions be disallowed by default
The benefits of a falsey NULL (any major drawbacks?)
Criteria for stable r3/ren-c releases
Philosophy of ANY and ALL w.r.t. voids
← previous page
next page →