programming-language

using Test
@test :(1 = 2) |> repr == Expr(:(=), 1, 2) |> repr == ":(1 = 2)"

but others (reserved) assignment ops are not shown as they are typed, eg in infix form but in prefix one.

@test :(1 := 2) |> repr == ":($(Expr(:(:=), 1, 2)))"

a small annoyance, but one that may easily be fixed by adding them to expr_infix_wide @ https://github.com/JuliaLang/juli

Depends on #3870/#12074.
Part of #10274.

Currently the only outputs available in assembler mode on the CLI are: --asm, --bin, --ir-optimized and --ewasm. settings.outputSelection in Standard JSON actually provides more (see [StandardCompiler::compileYul()](https://github.com/ethereum/solidity/blob/1e630fc5840bb12ad9bca2dcf1f6c534c9ba8d31/libsolidity/interface/StandardCompil

So currently, install in our "unix" Makefile isn't hooked into cmake so it can lead to errors.

in particular if you do

make configure arch=not-our-default
make build
make install

you will end up with a broken install because the arch override from configure is used during build but isn't used during install, instead a different arch (our default) is used and you end

In unisonweb/unison#2280, I swapped ucm to use optparse applicative, which means we can now get Bash, Zsh, or Fish tab-completion on arguments and commands for free! This also allows configuring custom completion types within the CLI code, and if you use the appropriate parser type for arguments it can infer that a given argument must be a file or directory, etc.

You can

Motivation

When installing SuperCollider from fresh, it will by deffault recording the server output in the .aiff format unless changed ala s.recHeaderFormat_("wav") in a startup file.

AIFF is a more MacOS centric format and it just doesn't work as well on Linux for example when converting files, importing/exporting from other prog

Hello, I'm rewriting a small application in Mint and have found that there's no way (as far as I can tell) to access the Http response headers when using the built-in Http module. For my use case, I need to know the content type of the response so I can decide how to parse it.

I've run into this not just in my application but also when I'm using mint start during development; when I test my