New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add data frame/data table structure and associated module-capabilities (similar to Deedle) to the core data structures. #704

Open
sashababaei opened this Issue Oct 29, 2018 · 1 comment

Comments

Projects
None yet
2 participants
@sashababaei

sashababaei commented Oct 29, 2018

Add data frame/data table and associated module-capabilities (similar to Deedle) to the core data structures.

I propose we add optimised-for-big-data data frame/data table structures and associated module-capabilities (similar to Deedle) to the core data structures. They are the prevalent data structure to hold either input or output in the field of data science, and very natural and convenient to work with.

The existing way of approaching this problem in F# is through Deedle. As an example, I experience a very strange problem with the Deedle data frame and conversion to float, in an expression involving Array.Parallel.map. The odd thing was that code ran perfectly fine as an interactive script but would cryptically not compile and run as a source file.

Pros and Cons

The advantages of making this adjustment to F# is to make it a more capable and well-rounded tool for data science tasks. I believe F# has excellent potential and unique natural suitability for such a hot and ever-growing field. This would certainly be a good push in the right direction.

I see no disadvantages in making this adjustment to F#.

Please tick this by placing a cross in the box:

  • This is not a question (e.g. like one you might ask on stackoverflow) and I have searched stackoverflow for discussions of this issue
  • I have searched both open and closed suggestions on this site and believe this is not a duplicate
  • 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.

Please tick all that apply:

  • This is not a breaking change to the F# language design
  • I or my company would be willing to help implement and/or test this
@cartermp

This comment has been minimized.

Member

cartermp commented Nov 8, 2018

@sashababaei Could you provide some hypothetical examples (with code samples) of how this might look? Mostly interested in the programming model that you're interested in.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment