From 50ec8fd0ab245dd946ce45f0c4967f05e8ff2acc Mon Sep 17 00:00:00 2001 From: Dr Joe Average <57107933+drjoeavg@users.noreply.github.com> Date: Mon, 14 Sep 2020 21:41:08 -0400 Subject: [PATCH] Fix typos in README.md Various typos and a small bit of re-phrasing --- README.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/README.md b/README.md index bf72344..00bc2b2 100644 --- a/README.md +++ b/README.md @@ -83,9 +83,9 @@ alias q="query-json" ## Performance -[This report](./benchmarks/report.md) is not a exaustive performance report of both tools, it's a overview for the percived performance of the user. Here I don't profile each tool and trying to see what are the bootlenecks, since I asume that both tools have the penalty of parsing a JSON file. Simply run a bash script and analyze the results. +[This report](./benchmarks/report.md) is not an exhaustive performance report of both tools, it's a overview for the percieved performance of the user. Here I don't profile each tool and try to see what are the bootlenecks, since I assume that both tools have the penalty of parsing a JSON file. Simply run a bash script and analyze the results. -Aside from that, **q** isn't feature parity with **jq** which is ok at this point, but **jq** contains a ton of functionality that query-json misses and some of the **jq** operations aren't native, are builtin with the runtime. In order to do a proper comparision all of this above would need to take into consideration. +Aside from that, **q** doesn't have feature parity with **jq** which is ok at this point, but **jq** contains a ton of functionality that query-json misses and some of the **jq** operations aren't native, are builtin with the runtime. In order to do a proper comparision all of this above would need to take into consideration. The report shows that **q** is between 2x and 5x faster than **jq** in all operations tested and same speed (~1.1x) with huge files (> 100M). @@ -93,7 +93,7 @@ The report shows that **q** is between 2x and 5x faster than **jq** in all opera The purposes of this project were mostly 2: -- **Learn how to write a lexer/parser/compiler with the OCaml stack** using menhir and sedlex while trying to create a compiler with great error messages and possibly recoverability (currently _work in progress_). +- **Learn how to write a lexer/parser/compiler with the OCaml stack** using `menhir` and _`edlex` while trying to create a compiler with great error messages and possibly recoverability (currently _work in progress_). - **Create a CLI tool in Reason Native** and being able to distribute it as a binary, enjoy it's performance and try further with cross-compilation. ## Currently supported feature set: