programming-language

Currently, we mostly map julia function arguments directly to LLVM arguments regardless of how many there are. That probably causes us to hit some pathological cases, since LLVM is not likely to care about or optimize handling 1000 arguments, since most front-ends do not generate that.

For example:

julia> fields = [:($(Symbol("var$i"))::Int) for i in 1:1000];

julia> @eval struct x
   

Apparently we have the assert macro disabled in CI, even in non-release builds - at least on Windows (see ethereum/solidity#12634 (comment)). While this macro is generally discouraged in our project in favor of the solAssert() family of macros, we still do have them in some places and I think that they should

According to the Naming Rules in the tutorial:

After an underscore for private or special methods (behaviors, constructors, and functions), any method or variable, including parameters and fields, must start with a lowercase letter. In all cases underscores in a row or at the end of a name are not allowed, but otherwise, any comb

You can already do ucm version, but ucm --version is a pretty standard thing to be able to do, and I find that I keep typing it.

It's also expected by default for certain tools like help2man (though that one can be configured to look for ucm version).

Motivation

The .postf is a neat shortcut for posting a formatted string.

But personally I see my self doing things like "% is not implemented yet".format("something").warn and the equivalent with .error all the time.

Description of Proposed Feature

Add the following methods to String:

// Equivalent to .postf
St

A few days ago I decided to write a gleam package for password hashing and I decided on the argon2 algorithm. First, I had to publish an argon2 package for erlang because there wasn't any, so I published argon2. It's a bunch of nifs using the argon2 crate. It works if you use it in your erl