[decimal] Rename Decimal as Decimal128 + Add default precision to BigDecimal as 36
#112
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This pull request introduces significant updates to the
README.mddocumentation and benchmarks for the DeciMojo library. The changes primarily focus on renaming theDecimaltype toDecimal128for clarity and consistency, updating aliases and examples accordingly, and improving benchmark scripts to reflect these changes.Documentation Updates:
Type Renaming and Aliases:
DecimaltoDecimal128to better reflect its 128-bit fixed-precision nature and updated its alias fromDectoDec128.Decimal128name and alias in various sections, including construction, arithmetic, rounding, and mathematical functions.Precision and Usage Details:
BigDecimaloperations and provided examples of how to configure precision using theprecisionargument.DecimaltoDecimal128and its characteristics.Benchmarking Instructions:
pixi run bench_decimaltopixi run bdecand adjusted the log file path to align with the new naming convention.Benchmark Script Updates:
Type Renaming:
benches/decimal/bench_add.mojotobenches/decimal128/bench_add.mojo.Decimalin the benchmark script toDecimal128, including variable names, function arguments, and comments.Benchmark Cases:
Decimal128for various scenarios, such as simple integers, high-precision decimals, and numbers requiring carrying.These updates improve clarity in the documentation, align the naming convention with the library's goals, and ensure that benchmarks accurately reflect the latest changes.