You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This issue was filed against Fable 3.7.0-beta. Based on a code review of the current Fable 4.x source, this bug appears to have been fixed.
Root cause (3.7.0-beta): The call path for a static operator on an [<AttachMembers>] type used getMemberDisplayName(memb) to look up the member name, which returns the F# operator symbol "+" for op_Addition. This caused the wrong property access Number$["+"] to be generated at the call site, while the declaration correctly used op_Addition.
Current behaviour (4.x): getAbstractMemberInfo in FSharp2Fable.Util.fs now uses memb.CompiledName (which returns "op_Addition") for non-getter/setter attached members. Both the declaration path (transformExplicitlyAttachedMember via FsMemberFunctionOrValue.CompiledName(memb)) and the call path now agree on "op_Addition", so the generated code uses the correct identifier.
If you're still seeing this with a current Fable release, please reopen and share a minimal repro. Otherwise, feel free to close this issue.
Activity
github-actions commentedon Apr 21, 2026
🤖 This is an automated response from Repo Assist.
This issue was filed against Fable 3.7.0-beta. Based on a code review of the current Fable 4.x source, this bug appears to have been fixed.
Root cause (3.7.0-beta): The call path for a static operator on an
[<AttachMembers>]type usedgetMemberDisplayName(memb)to look up the member name, which returns the F# operator symbol"+"forop_Addition. This caused the wrong property accessNumber$["+"]to be generated at the call site, while the declaration correctly usedop_Addition.Current behaviour (4.x):
getAbstractMemberInfoinFSharp2Fable.Util.fsnow usesmemb.CompiledName(which returns"op_Addition") for non-getter/setter attached members. Both the declaration path (transformExplicitlyAttachedMemberviaFsMemberFunctionOrValue.CompiledName(memb)) and the call path now agree on"op_Addition", so the generated code uses the correct identifier.If you're still seeing this with a current Fable release, please reopen and share a minimal repro. Otherwise, feel free to close this issue.