-
Notifications
You must be signed in to change notification settings - Fork 22
Description
I propose we ... (describe your suggestion here)
Allow yielding from a do block. E.g.
[
do
let item00 = ...
let item01 = ...
yield (item00, item01)
do
let item10 = ...
let item11 = ...
yield (item00, item11)
]This currently gives the error
FS0747 "This construct may only be used within list, array and sequence expressions, e.g. expressions of the form 'seq { ... }', '[ ... ]' or '[| ... |]'. These use the syntax 'for ... in ... do ... yield...' to generate elements"
Do blocks are nice because they allow things to be defined in smaller scopes.
The existing way of approaching this problem in F# is ...
Use a match expression (very ugly)
[
match () with
| () ->
let item00 = ...
let item01 = ...
yield (item00, item01)
match () with
| () ->
let item10 = ...
let item11 = ...
yield (item00, item11)
]Or put everything in one scope
let item00 = ...
let item01 = ...
let item10 = ...
let item11 = ...
[
(item00, item01)
(item10, item11)
]Pros and Cons
The advantages of making this adjustment to F# are ...
Allow defining items to be placed in lists in a smaller scope.
The disadvantages of making this adjustment to F# are ...
None
Extra information
Estimated cost (XS, S, M, L, XL, XXL): S/M
Related suggestions: (put links to related suggestions here)
Affidavit (please submit!)
Please tick these items by placing a cross in the box:
- [ x ] This is not a question (e.g. like one you might ask on StackOverflow) and I have searched StackOverflow for discussions of this issue
- [ x ] This is a language change and not purely a tooling change (e.g. compiler bug, editor support, warning/error messages, new warning, non-breaking optimisation) belonging to the compiler and tooling repository
- [ x ] This is not something which has obviously "already been decided" in previous versions of F#. If you're questioning a fundamental design decision that has obviously already been taken (e.g. "Make F# untyped") then please don't submit it
- [ x ] I have searched both open and closed suggestions on this site and believe this is not a duplicate
Please tick all that apply:
- [ x ] This is not a breaking change to the F# language design
- [ x ] I or my company would be willing to help implement and/or test this
For Readers
If you would like to see this issue implemented, please click the 👍 emoji on this issue. These counts are used to generally order the suggestions by engagement.