최근 완료된 8시간 회차 사이 GitHub 스타 증가량 순
Qwen3.5‑4B 전용 조향형 뉴런 탐색기, 모든 MLP 뉴런을 밀어 결과를 보관·탐색
Rust 코드를 실시간으로 편집하고, 실행 중인 프로그램에서 밀리초 단위로 변화를 확인
TraceRoot는 오픈소스 에이전트‑네이티브 개선 레이어로, 생산 추적·탐지 신호·평가를 코딩 워크플로에 통합합니다
대만 제작, 단일 Go 바이너리 자체 호스팅 AI 에이전트, 도구 작성·테스트·MCP로 Claude Code·Codex 공유
대형 AI 모델을 내 PC에서 실행: Strata 엔진에서 Qwen3.8‑Flash‑Next, GLM 5.3 Flash 등 다양한 모델 지원
A flow-style query language for SQL engines
저장소 README에서 가져옴
README 전체를 불러오는 중입니다. 아래는 저장된 발췌입니다.
Wvlet, pronounced as weave-let, is a new cross-SQL flow-style query language for functional data modeling and interactive data exploration. Wvlet works with various types of SQL-based database engines, including DuckDB, Trino, Hive, etc.README 전문 보기 ↗Wvlet, pronounced as weave-let, is a new cross-SQL flow-style query language for functional data modeling and interactive data exploration. Wvlet works with various types of SQL-based database engines, including DuckDB, Trino, Hive, etc.
AI coding agents: the docs are available as plain text at llms.txt (index) and llms-full.txt (all pages).
Wvlet queries (saved as .wv files) provide a natural way to describe data processing pipelines, which will eventually be compiled into a sequence of SQL queries. While SQL is a powerful language for processing data, its syntax often does not match the semantic order of data processing. Let's see the following example: The syntactic order of SQL's SELECT ... statements mismatches with the actual data flow inside the SQL engines (cited from A Critique of Modern SQL And A Proposal Towards A Simple and Expressive Query Language (CIDR '24)):
For overcoming this shortcoming of SQL, Wvlet starts from a table scan statement from ..., and the result can be streamlined to the next processing operators like where, group by, select, etc., as if passing table values through a pipe to the next operator:
from (table)
where (filtering condition)
...
where (more filtering condition can be added)
group by (grouping keys, ...)
where (group condition can be added just with where)
select (columns to output)
order by (ordering columns...)
limit (limiting the number of output rows)
With this flow style, you can describe data processing pipelines in a natural order to create complex queries. You can also add operators for testing or debugging data in the middle of the query. This flow syntax is gaining traction and has been adopted in Google's SQL to simplify writing SQL queries. For more details, see SQL Has Problems. We Can Fix Them: Pipe Syntax In SQL (VLDB 2024).
Many thanks to everyone who has contributed to our progress: