From 1ef94acec11b6f33795455ca47f43f8e62652259 Mon Sep 17 00:00:00 2001 From: Nicholas Bishop Date: Sat, 2 May 2015 19:15:00 -0400 Subject: [PATCH] Fix a missing word in the README --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 74ed52129a4..54a8bfc4c2f 100644 --- a/README.md +++ b/README.md @@ -88,7 +88,7 @@ when making those changes. The advantage of the tokens approach are that you can operate on non-parsable code. I don't care too much about that, it would be nice, but I think being able -to sophisticated transformations is more important. In the future I hope to +to perform sophisticated transformations is more important. In the future I hope to (optionally) be able to use type information for informing reformatting too. One specific case of unparsable code is macros. Using tokens is certainly easier here, but I believe it is perfectly solvable with the AST approach. At the limit,