scarf

this can be workaround using watch or hmr. 1. run `echo 'import "lume/cli.ts"' > _main.ts` on terminal. 2. change tasks in `deno.json` to following: ```diff "tasks": { - "lume": "echo...

``` site.process([".js"], (pages) => { for (const page of pages) { if (!page.content) return console.log(page.content) page.content = (page.content as string).replace( re, (line) => line.replace(/"(\..*)\.tsx?/, '"$1.js'), ) } }) ``` This...

Similarly, printing functions in GHCI also creates confusing error messages: ## Reproduction ```hs λ> add x y = x + y add :: Num a => a -> a ->...

> "Write full sentences" and "write as little as possible" are in conflict. I don't see a great principle in this space -- we just need to use good judgement....

> I do still think this is not a responsibility of GHC itself, though. Maybe the best place to put those kinds of contextual hints is in a HLS plugin?...

i think it's okay to allow `Path"/usr" / stdin.readLine`. also python equivalent: ```py In [1]: from pathlib import Path ...: from sys import stdin In [2]: Path('usr') / stdin.readline() bin...

is 'reading from stdin' is type unsafe? because `Path"/usr" / stdin.readLine` feels type safe enough for me

> which includes all sorts of strings which can not represent valid path could something like this solve the safety issue? ```nim func `/`(head: Path, tail: Path | string): Path...

make sense, but wouldn't readLine problem apply to current implementation too? ```nim Path"foo" / Path stdin.readLine ```

could i get doc for `string{lit}`? I wasn't able to find it in the [nim manual](https://nim-lang.org/docs/manual.html#lexical-analysis-string-literals), and its syntax certainly isn't pragma