ExtCore icon indicating copy to clipboard operation
ExtCore copied to clipboard

An extended core library for F#.

Results 19 ExtCore issues
Sort by recently updated
recently updated
newest added

The result of PR #50 has lead to the main branch being now in an error state, see https://travis-ci.org/jack-pappas/ExtCore. ![image](https://user-images.githubusercontent.com/16015770/179375050-bcde1163-e121-4bbc-adda-b0d6a7cc4732.png) The log appears to be erased, so I cannot see...

Once the [Maintainability tasks](https://github.com/jack-pappas/ExtCore/projects/1) project is completed, I think we ought to release the new versions of _ExtCore_ as v1.0.0. The reason for the version bump is that the library...

maintenance

- Forked individual files from #31 and reverted original files - Added `Compatibility` namespaces and moved some `Choice` constructs into these - Renamed `Notification.Error` to `Notification.Exception` in order to avoid...

### Proposal This PR introduces atomic cells (similar to F# ref cells), that enable thread-safe atomic operations - based on Interlocked and Volatile capabilities, without expensive locking (with caveats regarding...

_ExtCore_ has some features requiring the library to be built using the F# proto-compiler (``fsc-proto``), most notably the 'tagged' collections types (such as ``TagMap``) and their supporting modules. I've found...

maintenance

`==` refers to obsolete use `===` `===` refers to obsolete use `==` https://github.com/jack-pappas/ExtCore/blob/master/ExtCore/Pervasive.fs#L105-L113

maintenance

For _ExtCore_ 1.0, consider replacing the ``substring`` type in favor of the new ``ReadOnlySpan`` type. ``substring`` is useful for avoiding allocations in text-processing code, but unfortunately there are some inconsistencies...

enhancement
proposal

For _ExtCore_ v1.0 -- should we support both the ``Result`` and ``Choice`` type for error-handling, or should we drop ``Choice`` and use only ``Result``? Pros/cons of supporting ``Result`` only: *...

maintenance

Issues like #39 and @wallymathieu's work in #31, #32 raise an important question: should _ExtCore_ support/target multiple versions of _FSharp.Core_? If not, what should be the policy for determining which...

maintenance

It'd make releasing new versions of _ExtCore_ significantly easier if we could build + release new versions of the nuget package directly from within the CI builds. Some initial thoughts:...

maintenance