James Clark
James Clark
The first idea that comes to mind for this is to have a library function with a parameter of type `map`, which would: 1. wait for one future to complete...
Is the user problem specifically in resource paths? Changing syntax for identifiers generally is going to be very constrained by compatibility issues. There's more scope for a more flexible syntax...
It would be difficult to extend the syntax in the client-resource-access-action, because that occurs nested within other constructs and isn't always followed by an opening parenthesis, so a resource-method-name can...
Another possibility is to allow the user to provide the HTTP listener with a `split` function that the HTTP listener will call to split the URL into segments, instead of/in...
I think we could target this for 2023R2.
This is one of the cases that `do/on fail` was designed to handle: ``` do { check doA(); check doB(); } on fail var e { return error ("Something happened",...
We could add an expression-oriented `on fail` clause to check, so ``` check doA() on fail e => error("Something happened", e, c1 = c1, c2 = c2); ``` desugars to...
We should address #1178 before moving out of Preview.
@sanjiva The semantic of `check E` are 1. Evaluate E to get value v 2. If v is an error, the expression completes abruptly with a check-fail with associated value...
Given that `check` is an expression (you can do `check doA(check foo(), check bar())`), if we want to enhance `check` we need to do this an expression. The language doesn't...