chore: update syntax

[peter-jerry-ye]

No description provided.

[peter-jerry-ye-code-review]

Inconsistent method conversion pattern across files

Category
Maintainability
Code Snippet
Lines like pub fn[T] Stack::clear(self : Stack[T]) -> Unit vs pub fn Stack::clear(self : Stack[T]) -> Unit
Recommendation
Ensure consistent placement of generic type parameters. For generic methods, the type parameter should come after the type name: pub fn Stack::[T]clear(self : Stack[T]) -> Unit or keep the current pattern consistently.
Reasoning
Mixed patterns for generic method syntax could lead to confusion and maintenance issues. The codebase should follow a single consistent pattern for method definitions with generics.

Potential breaking change in function signature format

Category
Correctness
Code Snippet
Functions like pub fn Decoder::consume(self : Decoder, input : BytesView,) -> String raise Error have trailing commas in parameter lists
Recommendation
Remove trailing commas from parameter lists or ensure they are consistently applied across all method definitions.
Reasoning
Trailing commas in parameter lists might not be supported in all contexts and could cause compilation errors. Consistency in formatting is important for maintainability.

Large-scale refactoring lacks focused scope

Category
Maintainability
Code Snippet
Changes span across 20+ files with 200+ modifications converting function syntax
Recommendation
Consider breaking this into smaller, module-focused pull requests (e.g., separate PRs for time/, crypto/, decimal/, etc.) to make reviews more manageable and reduce risk.
Reasoning
Large-scale mechanical changes across many modules increase the risk of introducing subtle bugs and make it difficult to thoroughly review each change. Smaller, focused changes are easier to validate and safer to merge.