question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

I think for V2.0 we can start discussing features here, before moving to a formal project.

What comes to my mind at the moment is:

  1. Remove subsumption from Applicatives: Right now seq “eats” all custom types implementing seq

  2. Same for Traversable, same situation: although this might not require a breaking change (todo find out)

  3. Implement IEnumerable for Vectors, now that (1) has to be done.

  4. New ListT monad transformer, possibly new SeqT as well, coded using a similar technique as the one used for Free Monads.

  5. Review computation expressions: autosense will be removed but we have to do something to make it easy for users to understand why a strict monad can’t be used with the non-strict CE. Maybe make compilation fail when calling a TryWith?

  6. Add ValueTuple, ValueTask and other latest addition to the framework. We can require a higher framework version

  7. Consider suggestions by @dsyme regarding using the return type for type inference.

Am I missing something?

EDIT

  1. Better task support (maybe an intermediate type like Step with conversions to/from Task and its use in Bind an other methods for task).

  2. Consistent type parameters order, this would need to swap type parameters in Validation<'err,'t> to Validation<'t,'err>.

Issue Analytics

  • State:open
  • Created 4 years ago
  • Reactions:4
  • Comments:26 (26 by maintainers)

github_iconTop GitHub Comments

2reactions
gustycommented, Oct 6, 2020

I’m a bit ambivalent about splitting the library.

It’s true, some users would like to see the extensions in a separate library, @dsyme for instance told me he likes that part of the library and would love to see it as a separate thing.

Let’s discuss that option in its corresponding issue https://github.com/fsprojects/FSharpPlus/issues/328#issuecomment-704095824 and assume in this discussion that the library will continue as a whole.

1reaction
gustycommented, Nov 7, 2020

To avoid using SRTPs on the result type, unless it’s the only way (ie: return, zero, maxValue).

We can try remove it in other functions, I’m sure it will be a breaking change, so we’ll have to measure the impact and see if it worths.

Read more comments on GitHub >

github_iconTop Results From Across the Web

UAM Airspace Research Roadmap Rev 2.0
This progression is largely drawn from the FAA. NextGen UAM Concept of Operations v1.0 [7] and existing UML definitions [1] but is adapted...
Read more >
EASA Artificial Intelligence Roadmap 2.0 - A human-centric ...
The EASA Artificial Intelligence Roadmap 2.0 outlines the Agency's vision for the safety and ethical considerations of AI in aviation. It ...
Read more >
FICAM Roadmap v2.0
Federal Identity, Credential, and Access Management (FICAM) Roadmap and Implementation. Guidance. Value Proposition. The purpose of this document is to provide ...
Read more >
terminal/doc/terminal-v2-roadmap.md at main
Priority* Scenario State 0 Settings UI ✔️ 0 Command palette ✔️ 1 Tab tear‑off 📝
Read more >
Roadmap to Reconciliation 2.0: Moving Communities into ...
Roadmap to Reconciliation 2.0 includes a new preface and a new chapter on restoration, which address the high costs for people of color...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found