V8
pyright
Our great sponsors
V8 | pyright | |
---|---|---|
55 | 135 | |
22,506 | 11,846 | |
1.1% | 2.9% | |
9.8 | 9.8 | |
6 days ago | 7 days ago | |
C++ | Python | |
GNU General Public License v3.0 or later | 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.
V8
-
Boehm Garbage Collector
https://chromium.googlesource.com/v8/v8.git/+/HEAD/include/c...
Due to the nature of web engine workloads migrating objects to being GC'd isn't performance negative (as most people would expect). With care it can often end up performance positive.
There are a few tricks that Oilpan can apply. Concurrent tracing helps a lot (e.g. instead of incrementing/decrementing refs, you can trace on a different thread), in addition when destructing objects, the destructors typically become trivial meaning the object can just be dropped from memory. Both these free up main thread time. (The tradeoff with concurrent tracing is that you need atomic barriers when assigning pointers which needs care).
This is on top of the safey improvements you gain from being GC'd vs. smart pointers, etc.
One major tradeoff that UAF bugs become more difficult to fix, as you are just accessing objects which "should" be dead.
-
The Everything NPM Package
> If that standard library would be written in JS, a new browser (or rather a new JS engine being a part of the browser) could just use some existing implementation
That sounds great, but I'm doubtful of the simplicity behind this approach.
If my understanding is correct, v8 has transitioned to C++[0] and Torque[1] code to implement the standard library, as opposed to running hard-coded JavaScript on setting up a new context.
I suspect this decision was made as a performance optimization, as there would obviously be a non-zero cost to parsing arbitrary JavaScript. Therefore, I doubt a JavaScript-based standard library would be an acceptable solution here.
-
C++23: Removing garbage collection support
C++ lets you write anything you can imagine, and the language features and standard library often facilitate that. The committee espouses the view that they want to provide many "zero [runtime] cost," abstractions. Anybody can contribute to the language, although the committee process is often slow and can be political, each release the surface area and capability of the language gets larger.
I believe Hazard Pointers are slated for C++26, and these will add a form "free later, but not quite garbage collection" to the language. There was a talk this year about using hazard pointers to implement a much faster std::shared_ptr.
It's a language with incredible depth because so many different paradigms have been implemented in it, but also has many pitfalls for new and old users because there are many different ways of solving the same problem.
I feel that in C++, more than any other language, you need to know the actual implementation under the hood to use it effectively. This means knowing not just what the language specifies, but can occaissionally require knowing what GCC or Clang generate on your particular hardware.
Many garbage collected languages are written in or have parts of their implementations in C++. See JS (https://github.com/v8/v8)and Java GC (https://github.com/openjdk/jdk/tree/36de19d4622e38b6c00644b0...)
I am not an expert on Java (or C++), so if someone knows better or can add more please correct me.
-
Abstract Syntax Trees and Practical Applications in JavaScript
Remember that we earlier established that every source gets parsed into an AST at some point before it gets compiled or interpreted. For example, platforms like Nodejs and chromium-based browsers use Gooogle's V8 engine behind the scenes to run JavaScript and of course, some AST parsing is always involved before the interpreter kicks in. I looked V8's source and I discovered it uses its own internal parser to achieve this.
-
Notes: Advanced Node.js Concepts by Stephen Grider
In the source code of the Node.js opensource project, lib folder contains JavaScript code, mostly wrappers over C++ and function definitions. On the contrary, src folder contains C++ implementations of the functions, which pulls dependencies from the V8 project, the libuv project, the zlib project, the llhttp project, and many more - which are all placed at the deps folder.
-
What does the code look like for built-in functions?
Here is the implementation of of Array. prototype.map in V8. It's written in a language called Torque which appears to be a special language just for the v8 engine.
-
is there any resource for JavaScript that explain what kind of logic statement behind each function and why it's give this output and only accept this input etc... ?
It sounds like you want to know how JavaScript is implemented in the browser. The thing is, there is no universal implementation for JavaScript. JavaScript defines a specification that must be adhered to, and then each browser vendor can implement it in whatever way they see fit, as long as it does the specified things. For example (and I'm not saying this is the case) it's entirely possible for Chrome to implement Array.sort() using merge sort, while Firefox implements it as quick sort. You can try to find the source code for the implementation in a certain browser, but that will not be universal. I imagine you can find out how it works in Chrome somewhere in https://chromium.googlesource.com/v8/v8.git, though I'm not sure exactly where.
- Minimize Heap Allocations in Node.js
-
[AskJS] Who first used the term "spread operator" re spread syntax ...?
chrome v8 commits referring to spread operator one of them: https://github.com/v8/v8/commit/93b3397e52d3faf38059718de335027e57b9690d
pyright
-
Enhance Your Project Quality with These Top Python Libraries
Pyright is a fast type checker meant for large Python source bases. It can run in a “watch” mode and performs fast incremental updates when files are modified.
-
Mypy 1.6 Released
Not exactly what you are looking for but maybe useful to others.
https://github.com/microsoft/pyright/blob/main/docs/mypy-com...
-
VSCodium – Libre Open Source Software Binaries of VS Code
You can use pyright instead[0]. It is the FOSS version of pyright, but having some features missing.
-
How do you enable semantic highlighting for Python?
Unfortunately, pyright explicitly stated that they are not interested in inlay hints or other language server features, that those will only be added to pylance. That's why I added it myself instead of submitting a pull request to pyright. See https://github.com/microsoft/pyright/issues/4325
-
How do I enable an LSP for json files?
return { -- add pyright to lspconfig { "neovim/nvim-lspconfig", ---@class PluginLspOpts opts = { ---@type lspconfig.options servers = { -- Listed servers will be automatically loaded to buffers jsonls = { settings = { json = { format = { enable = true, }, }, validate = { enable = true }, }, }, pyright = { settings = { python = { analysis = { -- https://github.com/microsoft/pyright/blob/main/docs/settings.md autoSearchPaths = false, useLibraryCodeForTypes = true, diagnosticMode = "openFilesOnly", }, }, }, }, }, -- Add folding capability to use LSP for ufo plugin capabilities = { textDocument = { foldingRange = { dynamicRegistration = false, lineFoldingOnly = true, }, }, }, }, }, }
-
Pyright does not respect virtualenv (astronvim)
I don't use astro, but you can configure pyright by using a pyrightconfig.json or directly in the LSP configuration.
-
Eglot + pyright can not get completion on django.db.models
Not sure if pyright supports it unfortunately. I personally accepted the lack of support for attr.s and can't tell what the status on this actually is today. Here's a link to start reading up on the issue https://github.com/Microsoft/pyright/issues/146
- [Neovim] Quel Python LSP est le meilleur?
- [Neovim] ¿Qué Python LSP es mejor?
What are some alternatives?
jedi-language-server - A Python language server exclusively for Jedi. If Jedi supports it well, this language server should too.
mypy - Optional static typing for Python
python-lsp-server - Fork of the python-language-server project, maintained by the Spyder IDE team and the community
python-language-server - Microsoft Language Server for Python
coc-jedi - coc.nvim wrapper for https://github.com/pappasam/jedi-language-server
pylance-release - Documentation and issues for Pylance
ruff - An extremely fast Python linter and code formatter, written in Rust.
Duktape - Duktape - embeddable Javascript engine with a focus on portability and compact footprint
flake8
pyre-check - Performant type-checking for python.
ChakraCore - ChakraCore is an open source Javascript engine with a C API. [Moved to: https://github.com/chakra-core/ChakraCore]
Lua - Lua is a powerful, efficient, lightweight, embeddable scripting language. It supports procedural programming, object-oriented programming, functional programming, data-driven programming, and data description.