Real unit test (isolation, no children render)
Calls:
- constructor
- render
open Printf | |
(* Labeled arguments, the easy way *) | |
let _ = | |
(* Declare a function with labeled arguments like this: *) | |
let f ~x ~y = x + y in | |
(* Type: f : x:int -> y:int -> int *) | |
(* Call it like this: *) | |
printf "%d\n" (f ~x:5 ~y:6); |
Note This is a little out of date. Rust has made some progress on some points, however many points still apply.
Swift shares Rust's enthusiasm for zero-cost abstractions, but also emphasizes progressive disclosure. Progressive disclosure requires that language features should be added in a way that doesn't complicate the rest of the language. This means that Swift aims to be simple for simple tasks, and only as complex as needed for complex tasks.
author: @sleepyfox
title: The problem with AI coders
date: 22-Jun-2022
The problem with 'solutions' like GitHub's Copilot, and similar tech, is that it frames the problem as a problem of search. The programmer is searching for some code that does a thing (produce a HTML table with alternating coloured background rows of green and red), and that they just need to find that thing. Machine Learning has had success in this area, just look at Google's page-rank 'algorithm'.