You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What may be better or simplified?
build more optimal for-comprehansion of the Monadic Flow Type (without tailing 'v = ' for-enums).
Describe the solution
For the current mfc implementation with one monadic flow for: after the flattening result do postprocessing.
Do seq of tailing forv = optimization: move ones to the start of yield: yieldStats (new: see other issue ?) in each forCollector ...
This keeps semantic of the macro unchanged but makes produced code more effective.
Tests
should pass without changes
The text was updated successfully, but these errors were encountered:
DO AFTER #10
Scope (class, macro, etc.)
Postprocessing of TmsExtracted (of 1 Monadic Flow for)
What may be better or simplified?
build more optimal for-comprehansion of the Monadic Flow Type (without tailing 'v = ' for-enums).
Describe the solution
For the current mfc implementation with one monadic flow
for
: after the flattening result do postprocessing.Do seq of tailing
for
v =
optimization: move ones to the start ofyield
: yieldStats (new: see other issue ?) in eachforCollector
...This keeps semantic of the macro unchanged but makes produced code more effective.
Tests
should pass without changes
The text was updated successfully, but these errors were encountered: