cl-ppcre
aoc2022
cl-ppcre | aoc2022 | |
---|---|---|
13 | 9 | |
292 | 2 | |
0.0% | - | |
4.6 | 10.0 | |
about 1 month ago | over 1 year ago | |
Common Lisp | Julia | |
BSD 2-clause "Simplified" License | - |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
cl-ppcre
-
Compile time regular expression in C++
I've never used cl-ppcre myself, but its docs[1] claim that it provides compile-time regexes:
> CL-PPCRE uses compiler macros to pre-compile scanners at load time if possible. This happens if the compiler can determine that the regular expression (no matter if it's a string or an S-expression) is constant at compile time and is intended to save the time for creating scanners at execution time (probably creating the same scanner over and over in a loop).
[1]: https://edicl.github.io/cl-ppcre/
- Ask HN: What are some of the most elegant codebases in your favorite language?
-
sbcl and Let Over Lambda
A few weeks back Xach recommended cl-ppcre which i found educational.
-
-🎄- 2022 Day 1 Solutions -🎄-
For simple string processing, there are some functions in the language, that you can find listed here (for string-specific functions) and here (for more generic sequence-handling functions). For anything involving regular expressions, cl-ppcre is the way, in particular the split and register-groups-bind functions.
-
The unreasonable effectiveness of f-strings and re.VERBOSE
I must have a serious bug in my writing about this, because this was never about regex engines -- it's about literals and domain-specific sublanguages in general. Composing DSL programs by string concatenation is such a famous source of security bugs you see it in top-10 lists. I linked to the very similar example of a PEG parsing DSL.
But any regex engine that can work with a parse tree shows the same principle, e.g. https://edicl.github.io/cl-ppcre/#create-scanner2
-
Adding Space to subst function
Take a look at - https://github.com/edicl/cl-ppcre
-
Common Lisp ASDF maintainer considers resignation
And here's what I believe represents the reality of the situation... Stas was indeed tired of ASDF's changes. Now the nature of what changes to make is a matter of judgement of course, but in this case (I'm thinking of SBCL's bug report request to update ASDF: https://bugs.launchpad.net/sbcl/+bug/1826074), it would be a different matter altogether if the discussion was centered on how best to make the new ASDF work with SBCL, but the thread reads to me like a man who had to put up with too much breakage for the upteenth time. Now, if (for the sake of argument :D) the change was of the necessary kind -- think hardware changes or security issues -- I can still see myself feeling wronged, it's human to do so. Because I don't trust ASDF anymore or I feel as if they (or other people at each step of the process) have not shared enough of the burden. But from the discussions I have read (https://github.com/edicl/cl-ppcre/pull/30) what the ASDF maintainers want to change does not seem unreasonable and they are willing to share the burden. But let us say it's truly a 50/50 deadlock. Well then Linus is right, show us the code, who dares wins. And Stas certainly has enough on his plate. But that's why we must cooperate. You don't have to be a diplomat to know the difference when two people want to work together and when one party wants out. And this setting makes more sense when you read (https://bugs.launchpad.net/sbcl/+bug/1823442) where Stas honestly states he wants nothing more to do with ASDF. I don't think it's unreasonable to surmise there's a bit more going on here than plainly technical issues.
-
Stas has alienated long-time ASDF maintainer Robert Goldman
Could you just direct me to some existing discussions, in order to save time? I already read this one.
-
#"<your literal interpretation here>" (regular expression literals)
I plan to use the regular expressions with a cl-ppcre wrapper, also emulating various clojure regular expression operations. Similar to re21, which doesn't quite support the operations in the way I'd like (or match the clojure operations), and whose regular expression literal syntax is "#//".
aoc2022
-
-🎄- 2022 Day 12 Solutions -🎄-
Julia
-
-🎄- 2022 Day 8 Solutions -🎄-
Julia. Made a lot of silly mistakes - misread problem, off-by-ones, plus some bad indexing and data structures in Julia. All good lessons!
-
-🎄- 2022 Day 7 Solutions -🎄-
Julia. Finally too many new things to learn at once in Julia to avoid getting ugly.
- -🎄- 2022 Day 5 Solutions -🎄-
- -🎄- 2022 Day 4 Solutions -🎄-
- -🎄- 2022 Day 3 Solutions -🎄-
-
-🎄- 2022 Day 2 Solutions -🎄-
My second day with Julia. I'm learning a lot from other Juliarians, so hopefully my naive fresh take is always somehow interesting!
-
-🎄- 2022 Day 1 Solutions -🎄-
So I added some profiling and a single pass implementation. Had to go x10000 input size to see much impact, and even then:
What are some alternatives?
sbcl - Mirror of Steel Bank Common Lisp (SBCL)'s official repository
aoc2022 - Advent of Code 2022 on SCAMP
one-more-re-nightmare - A fast regular expression compiler in Common Lisp
advent-of-code-2022
aoc2022
advent-of-code-2022 - C# solutions for Advent of Code 2022
advents-of-code - 🎄🎁 Solutions for the yearly advent of code challenges
advent-of-code-2022 - Common lisp solutions to Advent of Code 2022
advent-of-code-2022 - back to rust, except i'll use libs where it makes sense
AdventOfCode-2022 - Advent of Code 2022 solutions. Enjoy :-)
advent-of-code - All my advent of code projects
advent_of_code - Advent of Code 2015 written in rust