fsharp / fsharp/fslang-suggestions

Support using `nameof` to generate literal strings (specifically in Attribute parameter lists).

Open
#1,348 3 comments 4 reactions 0 assignees View on GitHub
Dominant language
No language data
Stars
373
Forks
21
PR merge metrics
No merged PRs in 30d

Description

**I propose we** allow the `nameof` function to work at compile time, specifically in attribute parameter expressions like the following:

```fsharp
/// Represents information about programming constructs like variables, classes,
/// interfaces etc.
type SymbolInformation =
{
....
/// Tags for this symbol.
Tags: SymbolTag [] option

/// Indicates if this symbol is deprecated.
/// @deprecated Use tags instead
[.Tags) + " instead")>]
Deprecated: bool option
....
}
```

**The existing way of approaching this problem in F# is** to hard code member names in the strings, leaving them prone to drift out of date.

## Pros and Cons

**The advantages of making this adjustment to F# are** more uniform behavior of the nameof helper.

**The disadvantages of making this adjustment to F# are** expansion of the set of data that is computable at compile time, user confusion around when certain functions can be used.

## Extra information

**Estimated cost (XS, S, M, L, XL, XXL):** M

**Related suggestions:** https://github.com/fsharp/fslang-suggestions/issues/1347

## Affidavit (please submit!)

Please tick these items by placing a cross in the box:
* [x] This is not a question (e.g. like one you might ask on [StackOverflow](http://stackoverflow.com)) and I have searched StackOverflow for discussions of this issue
* [x] This is a language change and not purely a tooling change (e.g. compiler bug, editor support, warning/error messages, new warning, non-breaking optimisation) belonging to [the compiler and tooling repository](https://github.com/dotnet/fsharp)
* [x] 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
* [x] I have [searched both open and closed suggestions on this site](http://github.com/fsharp/fslang-suggestions/issues) and believe this is not a duplicate

Please tick all that apply:
* [x] 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

## For Readers

If you would like to see this issue implemented, please click the :+1: emoji on this issue. These counts are used to generally order the suggestions by engagement.

Contributor guide

No contributing guide indexed for this repository

Research direction

Start by reviewing the proposed Attribute example and the related suggestion #1347, then compare current nameof behavior with attribute parameter expression rules. A complete change would define the compile-time behavior and demonstrate that the example is accepted while producing the intended literal string.

Written by the indexing model from the issue text.

Assessment

Tech stack
fsharp
Domain
compilers
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
28/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.