funny_falcon | 1 year ago | on: Europe's most wanted man plotted my murder and that of my colleague
funny_falcon's comments
funny_falcon | 1 year ago | on: The Pentium contains a complicated circuit to multiply by three
funny_falcon | 1 year ago | on: From C++ to Clojure: Jank language promises best of both
funny_falcon | 1 year ago | on: Ropey – A UTF8 text rope for manipulating and editing large text
funny_falcon | 1 year ago | on: C: Simple Defer, Ready to Use
returns_struct looks actually correct to me, ie it is expected (by me). Golang's defer works this way.
Do both examples follow standard? Or is it common misinterpretation by all compilers?
funny_falcon | 1 year ago | on: Rails for everything
funny_falcon | 1 year ago | on: C++ is an absolute blast
funny_falcon | 1 year ago | on: C++ is an absolute blast
funny_falcon | 1 year ago | on: Float Self-Tagging
funny_falcon | 1 year ago | on: Float Self-Tagging
https://github.com/ruby/ruby/commit/b3b5e626ad69bf22be3228f8...
funny_falcon | 1 year ago | on: Float Self-Tagging
funny_falcon | 1 year ago | on: Float Self-Tagging
Edit: the commit https://github.com/ruby/ruby/commit/b3b5e626ad69bf22be3228f8...
funny_falcon | 1 year ago | on: Float Self-Tagging
funny_falcon | 1 year ago | on: Lush: My favorite small programming language
funny_falcon | 1 year ago | on: A high-performance, zero-overhead, extensible Python compiler using LLVM
Reproducibility matters for tests, they become simpler. Some other algorithms become simpler as well.
LRU is just a dict with preserving order: on access just delete and insert again.
funny_falcon | 1 year ago | on: 500 Python Interpreters
funny_falcon | 1 year ago | on: Telegram founder Pavel Durov arrested at French airport
So unless you’ve built application by yourself, you have no guarantee of it’s sequrity.
funny_falcon | 1 year ago | on: Show HN: High-precision date/time in SQLite
funny_falcon | 1 year ago | on: Show HN: High-precision date/time in SQLite
Extensible type system is a worst thing that could happend with database end-user performance. Then one may not short-cut no single thing in query parsing and optimization: you must check type of any single operand, find correct operator implemenation, find correct index operator family/class and many more all through querying system catalog. And input/output of values are also goes through the functions, stored in system catalog. You may not even answer to "select 1" without consulting with system catalog.
There should be sane set of builtin types + struct/json like way of composition. That is like most DBs do except PostgreSQL. And I strongly believe it is right way.
funny_falcon | 1 year ago | on: Go is my hammer, and everything is a nail