Category Features

Shared pointers to immutable objects

Personally I find the very conception of immutable variables very oxymoronic and illogical. When “immutable variable” is a field, it doesn’t work as immutable in some cases: at least in constructors and in deserialization logic. It prevents objects from delegating…

General info about types

Type deduction for fields, lambda parameters, results, local variables and constants Every value in Argentum has statically assigned type. For fields, constants, variables and lambda prototypes compiler deduces their types automatically by their initial values: Explicit type declarations: Only function/method…

Pointer types

In contrast with C++ or Rust Argentum pointers always point to class instance or interface instance. They cannot point to local variables or object fields. This is much like references in Java In contrast with Java and other GC-based languages…

Primitive types

Argentum has very few primitive types: Argentum allows to work with 8-bit, 16-bit, 32-bit, 64-bit types in a raw data structures with the help of sys_Blob class. This is mostly useful for interop with C or other languages. When declaring…

Names and modules handling

Starting today Argentum got new rules for modules and name visibility. TL;DR Previously: Now: Examples All examples can be found in windows-demo #1 Basics #2 Friend of my friend… The SDL-FFI module contains the low-level function declarations implemented in C:…

Object lifetime management in Argentum. First look.

All nowadays programming languages fall in three possible categories on controlling object lifetimes, memory management and maintaining data structures: All these three approaches have something in common.  They all allow developers to create a mess out of data structures and…