-
I propose we add an operator or keyword which can be used to bind values in computation expressions deep inside expressions (potentially arbitrarily), similar to C#'s await keyword, which can be used …
-
I propose we allow `use` statements in Computation Expressions. such as follows
```fsharp
type PooledEntry ignore
module DeadPool =
let (|PooledEntry|) (x: PooledEntry) =
x.Entry
…
-
Minor issue
This currently reads as:
https://www.repronim.org/reproschema/schema/#computespecification
A JavaScript expression to compute a score from other variables.
This sort of presume…
-
Currently, function contracts allow for arbitrary expressions, including ones that allow for potential side effects.
This could result in a statement that modifies the input arguments to a function b…
-
I'm not sure if you are working on Async at the moment or not. I though I would put this forward as a possibility.
F# has a way of defining Async expressions within the language using a feature call…
-
[@Caementum] I'm not sure if you are working on Async at the moment or not. I though I would put this forward as a possibility.
F# has a way of defining Async expressions within the language using a…
-
F# includes support for what they call [computational expressions](https://docs.microsoft.com/en-us/dotnet/fsharp/language-reference/computation-expressions) which seems to be an extremely useful and …
-
In a big Fable project, after a big refactoring to introduce a convenience computation expression, the project started to take much longer to compile. The overhead came from the type checking phase of…
-
I'm opening this issue as a centralized place to discuss and review the current design of the generic Computation Expressions.
The main issue of the current design was highlighted by @cmeeren recen…
gusty updated
3 years ago
-
We talked with @johnberzy-bazinga about idea of using cexprs for defining schemas, i.e instead of current:
``` fsharp
let Person = Define.Object("Person", "description", [
Define.Field("firstName…