Try to enhance no std support

[Sieluna]

Currently, only loading module through file uses std. We can consider excluding this part to make lib support no-std.

[Sieluna]

A new entrance for builder, make import module with variant names easier.

[Sieluna]

@lum1n0us Can you give me some suggestions? I think this proposal would be helpful.

[lum1n0us]

Love it. We might rebase this after PR #102 has been merged.

---

I thought the idea was about creating the smallest possible program without using the standard library, but it appears to be going in a different direction. Am I wrong?

[Sieluna]

I thought the idea was about creating the smallest possible program without using the standard library, but it appears to be going in a different direction. Am I wrong?

I think what I've done aligns with the principles advocated by Rust. However, it was inspired by this discussion:
https://stackoverflow.com/questions/57611219/when-adding-no-std-to-a-library-are-there-any-disadvantages-or-complicati

[lum1n0us]

Library users certainly don't need to worry. If a library enables no_std, its users are not required to enable no_std as well. The compiler will manage it appropriately.

Using no_std is definitely a challenge for library developers, since core is a subset of the std crate. Without access to alloc and advanced features (like Vec and String), developers face many limitations in programming. However, libraries also gain strong compatibility and cross-platform capabilities by using no_std.