Zig aims to be a simple language. It is not easy to define what simple exactly means, but zig is also a low-level programming language that aims for c-compatibility. To reach this goal, it needs good semantics in its type system so that developers have a complete toolbox to manipulate data.
So types in zig are composable, but this can become rapidly overwhelming. See those examples. Are you able to understand them at a glance, as soon as you read them?
*const ?u8
?*const u8
*const [2]u8
| let rec eval = function | |
| | `Appl (m, n) -> ( | |
| let n' = eval n in | |
| match eval m with `Lam f -> eval (f n') | m' -> `Appl (m', n')) | |
| | (`Lam _ | `Var _) as t -> t | |
| let sprintf = Printf.sprintf | |
| (* Print a given term using De Bruijn levels. *) | |
| let rec pp lvl = function |
| trait Interp { | |
| type Repr<T>; | |
| fn lit(i: i32) -> Self::Repr<i32>; | |
| fn add(a: Self::Repr<i32>, b: Self::Repr<i32>) -> Self::Repr<i32>; | |
| } | |
| struct Eval; | |
| impl Interp for Eval { |
| ### colored and fuzzy go doc | |
| if which bat > /dev/null; then | |
| function _godoc() { | |
| if echo $1|grep -q -E "([a-zA-Z0-9/.-_]+)/.*\..*"; then | |
| go doc ${@} | bat -p -l go | |
| else | |
| go doc ${@} | bat -p -l md | |
| fi | |
| } | |
| else |
Python utility to delete in bulk all GitHub Actions runs for a given workflow, either current or legacy/since removed. The GitHub UI currently allows removal of individual workflow runs, but this becomes tedious with a bulk of previous runs.
Create a Personal access token allowing the workflow scope:
| object main extends App { | |
| object <<<<<<< { | |
| def HEAD(s: String) = this | |
| } | |
| implicit class StringOps(s: String) { | |
| def =======(i: Int) = s | |
| def >>>>>>>(i: Int) = i | |
| } |
I have been working on a modern typing training application for the last couple of days. One of the main motivations was to build an app with a modern UI and minimal distractions, enabling to fully focus on the training aspect. You can read more about the original idea and thought process here as well as some notes on iterating over the details here.
After adding some minimal auto close functionalities for the code training section, you can read about it here, another important feature was to make the text training part more entertaining.
I love Rust and I have used it daily for many years as my go-to language, but I do have my own list of grievances that give me enough itches to contemplate playing with my own language ideas! Esteban Kuber's tweet inspired me to compile these into a list, even if I don't consider myself a ‘hater’!
Do note that Rust was a product of it's time, and was under many constraints in during its development, and I don't begrudge the choices that were made. Many of these things I only really recognise myself in hindsight!