wincompose VS rust

Touche compose. Natif sous linux, et sous windows : https://github.com/samhocevar/wincompose

Julia has made symbol input manageable and lets you define infix operators for many of the Unicode symbols that make sense for that. [1] And JuliaMono was designed to support the symbols that Julia does. [2]

I generally do quite fine with my Compose Key configuration, though (even on Windows, where I use WinCompose). [3]

[1]: https://docs.julialang.org/en/v1/manual/unicode-input/

[2]: https://juliamono.netlify.app/

[3]: https://github.com/samhocevar/wincompose

On Windows, I use http://wincompose.info/ for all my special-character needs (and use the system compose key on Linux).

na windowsa jest sobie WinCompose

Credit to wincompose's GUI for inspiration, which provides similar functionality on Windows.

I’ve previously used a nice little tool called WinCompose for exactly that. Looks like it’s still going:

http://wincompose.info/

Malgré to, yo recomanda WinCompose o simil si tu es in Windows.

I use WinCompose which gives me the same compose-key functionality that's built into Linux. I've chosen one key on my keyboard to be the Compose key (I use Right-Alt, but you can pick any key that's convenient). Then I can type

Assuming you are on desktop/laptop:

The long-winded way is to use your OS's character map tool: find the glyph you want there and copy+paste. Under Windows 10+ there is the emoji keyboard (hit [win]+;) which also gives access to much more including super-/sub- script characters, which is a little more convenient than character map. Presumably other OSs have similar available too.

Better is to have support for a compose key sequence. Usually build in to Linux & similar, you just might have to find the setting to turn it on and configure what your compose key is. Under Windows I use http://wincompose.info/ and there are a couple of similar tools out there. In any case it is useful for more than super- and sub-scripts: accented characters & similar (áàäæçffñ), some fractions (¼,½,¾), other symbols (°∞™®↑↓←→‽¡¿⸘♥⋘»‱), and configurable too so you can make what you use most easiest to access (and if you are really sad like me you can do something https://xkcd.com/2583/ to type hallelujah too!).

If you haven't dipped your touch-typing fingers into Rust yet, you really owe it to yourself. Rust is a modern programming language with features that make it suitable not only for systems programming -- its original purpose, but just about any other environment, too; there are frameworks that let your build web services, web applications including user interfaces, software for embedded devices, machine learning solutions, and of course, command-line tools. Since a custom GitHub Action is essentially a command-line tool that interacts with the system through files and environment variables, Rust is perfectly suited for that as well.

Here's an example of someone citing a disagreement between CRT and shell32:

https://github.com/rust-lang/rust/issues/44650

This in addition to the Rust CVE mentioned elsewhere in the thread which was rooted in this issue:

https://blog.rust-lang.org/2024/04/09/cve-2024-24576.html

Here are some quick programs to test contrasting approaches. I don't have examples of inputs where they parse differently on hand right now, but I know they exist. This was also a problem that was frequently discussed internally when I worked at MSFT.

    #include 

> instead of choosing a certain numbered version of the random library (if I remember correctly) I let cargo download the latest version which had a completely different API.

Yeah, they didn't follow the instructions and got burned. I still think that multiple things went wrong simultaneously for that experience. I wonder if more prevalent uses of `#[doc(alias = "name")]` being leveraged by https://github.com/rust-lang/rust/pull/120730 (which now that I check only accounts for methods and not functions, I should get on that!) so that when changing APIs around people at least get a slightly better experience.

Almost fixed the compiler: https://github.com/rust-lang/rust/pull/123325

Rust: A secure, efficient, and modern programming language (omitting ten thousand words). You can simply follow the installation instructions provided on the official website.

Recently did something similar in Rust but for generating SVGs. We've adopted it for snapshot testing of cargo and rustc's output. Don't have a good PR handy for showing Github's rendering of changes in the SVG (text, side-by-side, swiping) but https://github.com/rust-lang/rust/pull/121877/files has newly added SVGs.

To see what is supported, see the screenshot in the docs: https://docs.rs/anstyle-svg/latest/anstyle_svg/

We strongly believe in Rust as a powerful language for building production-grade software, especially for systems like ours that run alongside Kubernetes.

The above Assert<{N % 2 == 1}> requires #![feature(generic_const_exprs)] and the nightly toolchain. See https://github.com/rust-lang/rust/issues/76560 for more info.