From 34b091ad4ab4bf5562b9977e92a927ccb9b3ec13 Mon Sep 17 00:00:00 2001 From: Glen Whitney Date: Mon, 26 Aug 2024 15:58:05 +0000 Subject: [PATCH] Update Home --- Home.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Home.md b/Home.md index cfb2785..0d26495 100644 --- a/Home.md +++ b/Home.md @@ -8,4 +8,4 @@ Here are some key ideas of how the plan will be accomplished. * Implementation will start with Husht == Rust, and use the tree-sitter grammar for Rust to produce tree-sitter parse trees for "Husht" (=Rust) code, which will be transformed into essentially the same trees as rustc_parse would produce (in Rust's own ast structure), and then use the rustfmt code generator to produce Rust code. In the other direction, we will use rustc_parse itself, and likely use algorithms from the prettyplease pretty printer to convert that to a tree-sitter concrete syntax tree, from which it is of course easy to generate "Husht" code. * Once that roundtrip is working, we will fork and diverge the Husht tree-sitter parse from its starting point identical to the Rust tree-sitter parser, to implement the syntax that will make Husht a pleasure to use. -[Examples](Examples) will serve to guide the development of the Husht syntax. +[Examples](Examples) will serve to guide the development of the Husht syntax. There are some [other ideas](Other) that didn't necessarily come up in the examples.