Some RFCs are missing from the RFC's overview: https://github.com/fsharp/fslang-design/blob/master/RFCs

[abelbraaksma]

I'm not sure how/when RFCs are being moved there, but I just noticed that a bunch of RFC's are missing in the overview (https://github.com/fsharp/fslang-design/blob/master/RFCs), leading to link-rot (see: dotnet/fsharp#7839, the OP had a link to the then-correct location, it's now only available on the "preview" branch, as found by @Happypig375's comment).

I think we should strive to be consistent/complete here and make sure all RFC's are listed there (there are some other missing numbers besides 1080). Or, if there are different collections and they ought to be moved, prevent link-rot by allowing redirects or something?

I'm not sure of the policy here, just saying I often hit a 404 when clicking on an RFC link in some issue, which isn't good for posterity.

Edit: I think I found the cause: c710945 (cc: @cartermp). I thought when moving stuff, that Github would update references, but apparently it doesn't. Do we have a better option?

[cartermp]

No, github doesn't auto-redirect. RFCs are moving to folders that represent their status in F# itself.

[abelbraaksma]

This old discussion can be closed. But I don’t seem to have the option to mark this as the answer, or close the thread for that matter.

[cartermp]

I don't think there's a way to close a discussion (or at least I lack permissions to do so).

[vzarytovskii]

I think, the only way is to convert it to issue and close it. Or at least it's the only one I've found.

[abelbraaksma]

Apparently, locking is possible / should be possible by the owner: community/community#28745, but I don’t see that option here. 🤔

Maybe having that available or not is a setting on the repo. Not having it means discussions stay open forever. In other repos, I do see these options. Ah well.

[abelbraaksma]

Close button is back, possibly because I have (slightly) more rights now lol (but it looks like it is still possible to comment after it is closed… ah well…)