magic | Experimental typed JVM Lisp inspired by Clojure | Functional Programming library

C# 10.0 introduces a new feature called global using directive (global using ;) which allows to specify namespaces to be implicitly imported in all files in the compilation. .NET 6 RC1 has this feature enabled by default in new project templates (see enable property in your .csproj).

For Microsoft.NET.Sdk.Web next namespaces should be implicitly imported (plus the ones from Microsoft.NET.Sdk):

• System.Net.Http.Json
• Microsoft.AspNetCore.Builder
• Microsoft.AspNetCore.Hosting
• Microsoft.AspNetCore.Http
• Microsoft.AspNetCore.Routing
• Microsoft.Extensions.Configuration
• Microsoft.Extensions.DependencyInjection
• Microsoft.Extensions.Hosting
• Microsoft.Extensions.Logging

UPD

To address your questions in comment:

At the moment of writing the generated file containing default imports will be inside the obj folder named something like ProjectName.GlobalUsings.g.cs.

To modify default imports you can add Using element to your .csproj file. Based on exposed attributes it allows several actions including addition and removal:

The boolean conversion operator for std::basic_istream is explicit. This means that instances of the type will not implicitly become a bool but can be converted to one explicitly, for instance by typing bool(infile).

Explicit boolean conversion operators are considered for conditional statements, i.e. the expression parts of if, while etc. More info about contextual conversions here.

However, a return statement will not consider the explicit conversion operators or constructors. So you have to explicitly convert that to a boolean for a return.

Without the %!columns on line three, the call to map is lazy and thus never gets evaluated (the %!columns call wants to check the current value of columns, which implies eagerness).

To more explicitly invoke eagerness, either use the eager statement prefix (shown below) or switch to a for loop, which is eager by default.

I think this code will behave the way you want it to:

Old x86-64 CPUs don't support lzcnt, so rustc/llvm won't emit it by default. (They would execute it as bsr but the behavior is not identical.)

Use -C target-feature=+lzcnt to enable it. Try.

More generally, you may wish to use -C target-cpu=XXX to enable all the features of a specific CPU model. Use rustc --print target-cpus for a list.

In particular, -C target-cpu=native will generate code for the CPU that rustc itself is running on, e.g. if you will run the code on the same machine where you are compiling it.

This issue is caused by Azure CLI version 2.30.0 which seemed to be rolled out MS hosted agents recently.

Hence I adapted all my Python scripts running on (MS and self) hosted agents to this model:

Here's a modified version of your code that does what you want it to:

You are almost there. You just need to also config the following (Don't forget to restart your VS):

I had a really quick attempt at this with Numba but have not checked it too thoroughly though the results seem about right:

This seems to work: