Skip to content
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

Understand what would "working better with F# records" would entail #10731

Closed
divega opened this issue Jan 19, 2018 · 2 comments
Closed

Understand what would "working better with F# records" would entail #10731

divega opened this issue Jan 19, 2018 · 2 comments

Comments

@divega
Copy link
Contributor

divega commented Jan 19, 2018

Filing this based on community feedback:

image

This is not necessarily something the EF team is planning to tackle directly but wanted to start this issue to gather more information from the F# community and potentially improve our understanding of gaps in other areas besides the obvious in code generation.

F# Records have some relevant characteristics that are different from classes, e.g.:

  • Immutable by default and terse copy and update syntax in the language
  • Reference types by default but can be structs
  • Structural equality
@bricelam
Copy link
Contributor

I think there has been some work to enable this in the efcore/EFCore.FSharp repo.

@ajcvickers
Copy link
Contributor

Note from triage: closing this in favor of work done on the efcore/EFCore.FSharp repo.

@ajcvickers ajcvickers removed this from the Backlog milestone Oct 27, 2021
@ajcvickers ajcvickers reopened this Oct 16, 2022
@ajcvickers ajcvickers closed this as not planned Won't fix, can't repro, duplicate, stale Oct 16, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants