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
   

Because header inclusion can be very deeply nested, "using namespace" directive located in header files can unexpectedly change the meaning of the code. It can also lead to the name collision. For instance, it is not possible to define isDigit function in CommonSyntaxTest.cpp.

TODO:

1. Remove [using namespace util;](https://github.com/ethereum/solidity/blob/develop/libsolidity/ast/ASTAnnotatio

ponyc/packages/encode/base64/base64.pony includes the following code:

  fun decode[A: Seq[U8] iso = Array[U8] iso](
    data: ReadSeq[U8],
    at62: U8 = '+',
    at63: U8 = '/',
    pad: U8 = '=')
    : A^ ?
  =>
    """
    Configurable decoding. The defaults are for RFC 4648. Missing padding is
    not an error. Non-base64 data, other than whitespace (which can appear at

When the user defines an invalid top-level term, the error message should give correct info about what is permissible.

https://github.com/unisonweb/unison/blob/6cbd464c0eae2bd3d0a355e09ffef0a409762086/parser-typechecker/src/Unison/PrintError.hs#L1265

Of course, if we want to bring back the namespace functionality, disregard! 😄

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