Attribute targets on records
Follow up: https://github.com/dotnet/fsharp/pull/17173
Records compiles down to a class or struct sharplab.
This PR enforces the new rules on records.
Old rules
- AttributeTargets.Class
- AttributeTargets.Interface
- AttributeTargets.Delegate
- AttributeTargets.Struct
- AttributeTargets.Enum
New Rules
- AttributeTargets.Class
- AttributeTargets.Struct when using
[<Struct>] - AttributeTargets.Class ||| AttributeTargets.Struct when using
[<RequireQualifiedAccess>]
Before sharplab
[<AttributeUsage(AttributeTargets.Class)>]
type ClassTargetAttribute() =
inherit Attribute()
[<AttributeUsage(AttributeTargets.Interface)>]
type InterfaceTargetAttribute() =
inherit Attribute()
[<AttributeUsage(AttributeTargets.Struct)>]
type StructTargetAttribute() =
inherit Attribute()
[<InterfaceTarget>] // Does not fail. It should
[<StructTarget>] // Does not fail. It should
[<ClassTarget>]
type Record = { Prop: string }
[<ClassTarget>] // Does not fail. It should
[<InterfaceTarget>] // Does not fail. It should
[<Struct>]
type StructRecord = { Prop: string }
After
[<AttributeUsage(AttributeTargets.Class)>]
type ClassTargetAttribute() =
inherit Attribute()
[<AttributeUsage(AttributeTargets.Interface)>]
type InterfaceTargetAttribute() =
inherit Attribute()
[<AttributeUsage(AttributeTargets.Struct)>]
type StructTargetAttribute() =
inherit Attribute()
[<InterfaceTarget>] // Fails as expected
[<StructTarget>] // Fails as expected
[<ClassTarget>]
type Record = { Prop: string }
[<ClassTarget>] // Fails as expected
[<InterfaceTarget>] // Fails as expected
[<Struct>]
type StructRecord = { Prop: string }
Checklist
- [x] Test cases added
- [x] Release notes entry updated
:heavy_exclamation_mark: Release notes required
:white_check_mark: Found changes and release notes in following paths:
Change path Release notes path Description src/FSharp.Coredocs/release-notes/.FSharp.Core/8.0.400.md src/Compilerdocs/release-notes/.FSharp.Compiler.Service/8.0.400.md
Ready for review
/azp run
Azure Pipelines successfully started running 2 pipeline(s).
[!CAUTION] Repository is on lockdown for maintenance, all merges are on hold.
Can you explain the
RequireQualifiedAccessreasoning here, maybe even in the comment as part of code?Is it only a temporary need caused by
new compiler + old FSharp.Corecombination, eventually to be removed?
@T-Gro So the check for RequireQualifiedAccess is not needed at all. Turns out that when you use dotnet build on FSharp.Compiler.Service it uses the FSharp.Core nuget as opposed to the project reference and that is why my unit test was failing locally.
Thanks for the review
Thanks! Appreciate your consistent and meticulous approach. Do you see the light at the end of the attributes tunnel?
Yes. I have 2 more PRs and then a RFC