F# Method signature

[CeciAc]

@SLAVONchick commented on Tue Mar 26 2019

Consider edit method signature in F# view mode static member TryParse : string * -> bool to static member TryParse: string -> bool * int. And other signatures so that it return bool * int

---

Сведения о документе

⚠ Не вносите правки в этот раздел. Это необходимо для связывания страницы сайта docs.microsoft.com с вопросом на GitHub.

• ID: 04a9b653-1243-1bad-96f9-975cbfac4216
• Version Independent ID: 0f2d885e-e6e5-ad21-c946-5480b37d2ba1
• Content: Int32.TryParse Method (System)
• Content Source: xml/System/Int32.xml
• Product: dotnet-api
• GitHub Login: @dotnet-bot
• Microsoft Alias: dotnetcontent

[CeciAc]

Hi team, I'm moving this here since the user is making a suggestion on the example
best regards

[mairaw]

Thanks @CeciAc. @cartermp can you look at this feedback related to F# signatures?

[danieljsummers]

This is correct; the type signature of x in let x = System.Int32.TryParse "" is bool * int. This should be pretty standard through all the TryParse methods, as that's how the out parameters are represented in F#.

[cartermp]

@danieljsummers Not quite. out parameters (that is, byrefs that are intended to give a result) will implicitly convert to a tuple for the TryParse methods, but the signature is not a tuple of string -> bool * int; it's string -> byref<int> -> bool.

[danieljsummers]

Thanks for clarifying.

Is there a way within the current docs structure to document those differences? I literally wrote code before replying on this thread. :) If that's an overall concept within the language, I didn't realize it; I just learned that "this is the way the TryParse methods work".

[carlossanlop]

@gewarren @joelmartinez @mimisasouvanh seems like an infra issue with how the F# signature is generated. Do we have an existing internal issue tracking this?