All geek questions in one place

.NET API Tips for Future Use with F #

I am developing a .NET API to allow developers to create RoboCup agents for a 3D simulated soccer league .

I am very pleased with how the API works with C # code, however I would like to use this project to improve my F # skill (which is currently based on reading, not on practice).

Therefore, I would like to ask what things I should consider when developing an API that should be used with both C # and F # code.

Some points.

  • I use matrix and vector math quite actively. They are currently immutable classes / structures.
  • The API currently defines several interfaces with consumer tools (for example:) IAgent, using instances of their implementations (for example:) MyAgentto build other API classes (for example:) new Client(myAgent).
  • The API fires events.
  • The API provides several types of delegates.
  • The API includes several enumerations.

I would like to release an API version as soon as possible and do not want to make significant changes to it later if I understand that with F # it is too difficult to work with F #. Any advice is appreciated.

+3
source share
1 answer

The best advice is probably trying to use the API from F #. :)

However, I think you have good sounds

  • API # F # API
  • / Func/Action , .
  • , , , ,
  • , API, , (, , " ", " " - , F # |>ignore s)

, F #. , F #, , , .

+3

Source: https://habr.com/ru/post/1748882/

More articles:


All Articles