ruchy 4.2.0

A systems scripting language that transpiles to idiomatic Rust with extreme quality engineering
Documentation 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64

# ADR-007: Standard Library Design Philosophy

## Status

Accepted

## Date

2024-04-15

## Context

Ruchy needs a standard library that:
- Provides common functionality out of the box
- Feels familiar to Python developers
- Leverages Rust's performance
- Supports both interpreted and transpiled modes

## Decision

We implement a **minimal, batteries-included** standard library with:

1. **Core modules**: Always available, no import needed
   - Basic types (int, float, string, bool)
   - Collections (list, dict, set)
   - I/O (print, input, file operations)

2. **Extended modules**: Import required
   - `math`: Mathematical functions
   - `json`: JSON parsing/serialization
   - `http`: HTTP client (async)
   - `csv`: CSV processing
   - `datetime`: Date/time handling

3. **Implementation strategy**:
   - Core: Implemented in Rust, exposed via trait
   - Extended: Mix of Rust and Ruchy

```rust
pub trait StdlibProvider {
    fn get_function(&self, name: &str) -> Option<NativeFunction>;
    fn get_module(&self, name: &str) -> Option<Module>;
}
```

## Consequences

### Positive

- Familiar API for Python developers
- Consistent behavior across execution modes
- Performance-critical code in Rust

### Negative

- Maintenance burden for stdlib
- Feature parity with Python impossible
- Documentation overhead

## References

- Python standard library documentation
- Rust std library design
- Lua minimal stdlib philosophy