I suggest we ...

Support for [<CLIEvent>] on modules

As the name suggests. You can create [<CLIEvent>]s on classes as both instance and static members but not on a module. As far as the consuming e.g. C# library, the fact we're using a module in F# is unknown; from the F# side it's a pity you have to create classes for this behaviour rather than more idiomatic modules.

5 votes
Vote
Sign in
Check!
(thinking…)
Reset
or sign in with
  • facebook
  • google
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Isaac Abraham shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →

    3 comments

    Sign in
    Check!
    (thinking…)
    Reset
    or sign in with
    • facebook
    • google
      Password icon
      Signed in as (Sign out)
      Submitting...
      • Isaac Abraham commented  ·   ·  Flag as inappropriate

        Understood. Perhaps a warning or error would be preferable to what you currently get though, which kind of falls between both options i.e. it compiles but generates something unexpected.

      • Don Syme commented  ·   ·  Flag as inappropriate

        Hi Isaac, my feeling is that requiring a class is consistent with the F# language design. CLIEvent is an object-programming feature - like properties, abstract members etc.

      F# Language

      Feedback and Knowledge Base