The approved suggestion was for print/printn, I should have noticed this earlier, my apologies
More significantly, the PR discussion has revealed significant concerns about the lack of a generic print. These concerns were much stronger than I realised. This in turn raised signficant questions about culture-aware formatting in both interpolated strings and %A, captured in https://github.com/fsharp/fslang-suggestions/issues/897. In further 1:1 discussion with @KevinRansom the complexities around the spec of a generic print were explored.
This PR tries to capture these as unresolved questions. However, I'm also aware that it leaves the RFC in a form of stalemate - the desire for a robust, well-specified generic print is very strong (so much so that a non-generic print is seen as problematic), but it is not a simple thing to iron out the wrinkles in the existin %A implementation on which this needs to be based. I actually think it's going to be hard to progress this until we resolve the wrinkles in https://github.com/fsharp/fslang-suggestions/issues/897.
@albert-du I'm sorry not to have properly reviewed the original RFC and predicted more of these concerns. I understand it leaves your implementing PR in a form of limbo. Let's discuss further in the discussion thread.
Clarifying unresolved issues
The approved suggestion was for
print/printn, I should have noticed this earlier, my apologiesMore significantly, the PR discussion has revealed significant concerns about the lack of a generic
print. These concerns were much stronger than I realised. This in turn raised signficant questions about culture-aware formatting in both interpolated strings and%A, captured in https://github.com/fsharp/fslang-suggestions/issues/897. In further 1:1 discussion with @KevinRansom the complexities around the spec of a genericprintwere explored.This PR tries to capture these as unresolved questions. However, I'm also aware that it leaves the RFC in a form of stalemate - the desire for a robust, well-specified generic
printis very strong (so much so that a non-genericprintis seen as problematic), but it is not a simple thing to iron out the wrinkles in the existin%Aimplementation on which this needs to be based. I actually think it's going to be hard to progress this until we resolve the wrinkles in https://github.com/fsharp/fslang-suggestions/issues/897.@albert-du I'm sorry not to have properly reviewed the original RFC and predicted more of these concerns. I understand it leaves your implementing PR in a form of limbo. Let's discuss further in the discussion thread.