codesearch
chrono
codesearch | chrono | |
---|---|---|
10 | 23 | |
3,422 | 3,133 | |
- | 1.5% | |
0.0 | 9.6 | |
almost 2 years ago | 5 days ago | |
Go | Rust | |
BSD 3-clause "New" or "Revised" License | GNU General Public License v3.0 or later |
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.
codesearch
- Regular Expression Matching with a Trigram Index
- How Google Code Search Worked
-
Ask HN: How do you search large code-base before adding a feature or fixing bug?
Whenever I work on huge codebase (think 1M+), I always reach for Russ Cox's codesearch https://github.com/google/codesearch. It requires indexing the codebase first, which takes 15 minutes or so, but after that searches are instant.
-
Improving GitHub Code Search
There is some older version that's open source, I haven't tried it and I don't know how much of today's code search is based on it.
https://github.com/google/codesearch
-
Facebook open sources Glean, its scalable code search and query engine
There's https://github.com/google/codesearch
-
Is there a reliable way to force google to include a search term as plain text on the result or is there a decent search platform with that feature?
If you want to find exact pieces of syntax then you should use a code search engine like GitHub's, Sourcegraph, or Google's codesearch. On the flip side, these won't be as good as Google for finding general ideas because they're focused more toward the precision of answers rather than giving you things that are related.
-
Postgres regex search over 10,000 GitHub repositories (using only a Macbook)
Check https://github.com/google/codesearch or https://swtch.com/~rsc/regexp/regexp4.html, this is actually possible.
chrono
- The Unix leap second mess
-
Getaddrinfo() on glibc calls getenv(), oh boy
The problem is that this effects higher languages too, because they often build on libc. And on some OSes, they don't have a choice, because the system call interface is unstable and/or undocumented).
For example in rust, multiple time libraries were found to be unsound if `std::env::set_env` was ever called from a multi-threaded program. See:
https://github.com/time-rs/time/issues/293 and https://github.com/chronotope/chrono/issues/499
https://github.com/rust-lang/rust/issues/27970
https://github.com/rust-lang/rust/issues/90308
- Choosing the Right Rust Web Framework: An Overview
-
ZeroVer: 0-Based Versioning
> I think library authors should be more relentless and break compatibility every few years. We just need some conventions to not do so very often.
I indeed did this years ago---I'm the original author of Chrono [1]---and it wasn't well received [2] [3] [4]. To be fair, I knew it was a clear violation of semantic versioning but I didn't see any point of obeying that until we've reached 1.0 so I went ahead. People complained a lot and I had to yank the problematic release. By then I realized many enough people religiously expect semantic versioning (for good reasons though) and it's wiser to avoid useless conflict.
[1] https://github.com/chronotope/chrono
[2] https://github.com/chronotope/chrono/issues/146#issuecomment...
[3] https://github.com/chronotope/chrono/issues/156
[4] https://github.com/chronotope/chrono/blob/main/CHANGELOG.md#...
-
Simple, fast and safety alternative for unzip
On that note, it would also be good to configure cargo-deny so that a CI pipeline and any maintainer can easily audit the current dependency versions. Sometimes CVEs require a new major semver (looking at you, time 0.1.x and thus chrono 0.4.x), so it's not enough to rely on people installing the tool with semver-compatible updates. Automatically auditing dependencies is really important, and given how easy cargo-deny makes it, I don't think many projects have any excuse not to configure it.
-
Is it unidiomatic/anti-pattern to use the return keyword ?
The example has been randomly taken from the [Chrono][https://github.com/chronotope/chrono/blob/main/src/offset/utc.rs] crate.
-
Will Rust drop dependency on libc and make direct system calls? when ? (Please don't mention no_std case)
libc isn't "just a wrapper". Is a massive legacy codebase filled with hacks, UBs and bugs: https://github.com/chronotope/chrono/issues/499
- chrono 0.4.20 has been released, fixing the RUSTSEC-2020-0159 issue
-
chrono 0.4.20-rc.1 has just been released!!
Would love to have people test this, you can leave feedback here: https://github.com/chronotope/chrono/issues/674.
-
Trying to learn about chrono, Duration, etc...
Security issues? I'm looking at the open issues, but haven't noticed any that seem to be security related (no security related labels either). What am I missing here?
What are some alternatives?
zoekt - Fast trigram based code search
time - The most used Rust library for date and time handling.
hound - Lightning fast code searching made easy
advisory-db - Security advisory database for Rust crates published through crates.io
Glean - System for collecting, deriving and working with facts about source code.
jelly-actix-web-starter - A starter template for actix-web projects that feels very Django-esque. Avoid the boring stuff and move faster.
mozsearch - Mozilla code search website. (Please file bugs in bugzilla at https://mzl.la/2YtXmoN)
opengrok - OpenGrok is a fast and usable source code search and cross reference engine, written in Java
chat - A telnet chat server
postgres-operator - Production PostgreSQL for Kubernetes, from high availability Postgres clusters to full-scale database-as-a-service.
rusqlite - Ergonomic bindings to SQLite for Rust