Attribute targets on records

[edgarfgp]

Follow up: #17173

Records compiles down to a class or structsharplab.

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>]

Before sharplab

[<AttributeUsage(AttributeTargets.Class)>]typeClassTargetAttribute()=inherit Attribute()[<AttributeUsage(AttributeTargets.Interface)>]typeInterfaceTargetAttribute()=inherit Attribute()[<AttributeUsage(AttributeTargets.Struct)>]typeStructTargetAttribute()=inherit Attribute()[<InterfaceTarget>]// Does not fail. It should[<StructTarget>]// Does not fail. It should[<ClassTarget>]typeRecord={ Prop:string }[<ClassTarget>]// Does not fail. It should[<InterfaceTarget>]// Does not fail. It should[<Struct>]typeStructRecord={ Prop:string }

After

[<AttributeUsage(AttributeTargets.Class)>]typeClassTargetAttribute()=inherit Attribute()[<AttributeUsage(AttributeTargets.Interface)>]typeInterfaceTargetAttribute()=inherit Attribute()[<AttributeUsage(AttributeTargets.Struct)>]typeStructTargetAttribute()=inherit Attribute()[<InterfaceTarget>]// Fails as expected[<StructTarget>]// Fails as expected[<ClassTarget>]typeRecord={ Prop:string }[<ClassTarget>]// Fails as expected[<InterfaceTarget>]// Fails as expected[<Struct>]typeStructRecord={ Prop:string }

Checklist

• Test cases added
• Release notes entry updated

[github-actions]

❗ Release notes required

---

✅ Found changes and release notes in following paths:

Change path	Release notes path	Description
src/FSharp.Core	docs/release-notes/.FSharp.Core/8.0.400.md
src/Compiler	docs/release-notes/.FSharp.Compiler.Service/8.0.400.md

[edgarfgp]

Ready for review

[psfinaki]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 2 pipeline(s).

[T-Gro]

Can you explain the RequireQualifiedAccess reasoning here, maybe even in the comment as part of code?

Is it only a temporary need caused by new compiler + old FSharp.Core combination, eventually to be removed?

[github-actions]

Caution

Repository is on lockdown for maintenance, all merges are on hold.

[edgarfgp]

Can you explain the RequireQualifiedAccess reasoning here, maybe even in the comment as part of code?

Is it only a temporary need caused by new compiler + old FSharp.Core combination, 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

[psfinaki]

Thanks! Appreciate your consistent and meticulous approach.
Do you see the light at the end of the attributes tunnel?

[edgarfgp]

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