Wasm implementation

[day01]

Description Currently, to utilize blackscholes-rust, we need to compile the application on a normal server. However, as the development landscape evolves, there is a significant shift towards using WebAssembly (Wasm) in both backend and frontend applications.

Proposal: I propose that we enable blackscholes-rust to be compiled into WebAssembly. This transition would align with the modern development trends and could provide several benefits including improved performance and portability across different platforms.

Steps to Achieve This:

• Rewrite Cpp Implementation in rust:
  • The current implementation includes 2-3 files written in Cpp.
  • Rewriting these files in Rust would not only facilitate the transition to wasm but also enhance the overall quality and performance of the application.
  • Set Up wasm Compilation

Benefits:

• Simplified implementation of rust, wasm n python into one module - blacksholes-rust
• Improved portability across different platforms, allowing the application to run seamlessly in various environments.

[hayden4r4]

I like this, I split this out initially because of some of the drawbacks of wasm, I wanted to maintain a "clean" codebase and then have a seperate wasm one. If we can port the cpp->rust and eventually combine wasm and non-wasm to a single codebase without making too many compromises on the cleanliness of the code that would be great

[day01]

Actually, my current solution is ready for mving to wasm by introduce js feature for Random function. I think it will be available in current month.

if it will be work fine I suggest to publish not only rust but rust, wasm n python module in single codebase, bcs it is real.