Skip to content

Migrate from F# to C# when possible #68

Closed
@buybackoff

Description

@buybackoff
  • Freeze any F# new development until tooling and interop is fixed (in VS15?)
  • Move common functionality from Collections to Core project
  • Move base Series and Cursor classes to the Core project and eliminate recursive types
  • Rename Spreads.Extensions project to Spreads, remove existing empty Spreads project. Logically Extensions should "extend" Spreads package and contain non-core functionality, e.g. time-zone conversion, advanced cursors implementation.

Existing F# code will mostly remain in Spreads, at least collections. Immutable collections are just perfect
fit for F# - they were the initial reason why it was used at all. But I use these collections in real world
almost never, because they are slower than even the SQLite-based persistent implementation of series in some
cases and they take 60+ bytes per a key-value pair. SortedMap and SortedChunkedMap are polished and well tested
to risk rewriting them and spend time (and also are good examples of high-performance imperative F#).

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions