vscode-gremlins
proposal
vscode-gremlins | proposal | |
---|---|---|
3 | 47 | |
191 | 3,378 | |
0.5% | 0.3% | |
5.8 | 6.3 | |
about 2 months ago | about 2 months ago | |
JavaScript | HTML | |
GNU General Public License v3.0 or later | BSD 3-clause "New" or "Revised" 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.
vscode-gremlins
-
Visuo studio has a plugin for detecting those invisible characters. https://github.com/nhoizey/vscode-gremlins You should look for one for your IDE.
-
Smuggling hidden backdoors into JavaScript with homoglyphs and invisible Unicode characters
PHPStorm detects \u3164 "HANGUL FILLER" but VS Code does not. I tried using the Gremlins plugin, but looks like it currently doesn't detect this confusable. Is there any alternative plugin or setting in VS code to help detect these characters?
-
Expectations for Generics in Go 1.18
On VSCode, I use the Gremlins extension which highlight all those suspicious characters.
https://github.com/nhoizey/vscode-gremlins
proposal
-
Lies we tell ourselves to keep using Golang
the most basic example was the declined proposal https://github.com/golang/proposal/blob/master/design/32437-...
Some people didn't like the "try" keyword it reminded them too much of exceptions, some people didn't like that they couldnt see a return inline (which was the purpose of the proposal in the first place).
it's not that there are no solutions. the main problem is the go team's insistence to have "one true way" (tm) of doing something and unfortunately this gap between people who want to see every return inline and people who want to see the clean solution separate from the error handling is not something that can be bridged by technical means. the only solution is to implement both ways and lets see which one wins.
-
Does Go Have Subtyping?
The conclusion is pretty weird to me.
Go does rely on monomorphization for generics, just like C++ and Rust. The only difference is that this is an implementation detail, so Go can group multiple monomorphizations without worrying about anything else [1]. This form of hybrid monomorphization is being increasingly common, GHC does that and Rust is also trying to do so [2], so nothing special for Go here.
On the other hand, explaining variance as a lifted polymorphism is---while not incorrect per se---also weird in part because a lack of variance is at worst just an annoyance. You can always make an adopter to unify heterogeneous types. Rust calls it `Box`, Go happens to call it an interface type instead. Both languages even do not allow heterogeneous concrete (or runtime) types in a single slice! So variance has no use in both languages because no concrete types are eligible for variance anyway.
I think the conclusion got weird because the term "subtyping" is being misused. Subtyping, in the broadest sense, is just a non-trivial type relation. Many languages thus have a multiple notion of subtyping, often (almost) identical to each other but sometimes not. Go in particular has a lot of them, and even some relation like "T implements U" is a straightforward record subtyping. It is no surprise that the non-uniform value representation has the largest influence, and only monomorphization schemes and hetero-to-homogeneous adapters vary in this particular group.
[1] https://github.com/golang/proposal/blob/master/design/generi...
[2] https://rust-lang.github.io/compiler-team/working-groups/pol...
- Backward Compatibility, Go 1.21, and Go 2
-
Defining interfaces in C++ with ‘concepts’ (C++20)
https://github.com/golang/proposal/blob/master/design/generi...
-
Why Turborepo is migrating from Go to Rust – Vercel
Go Team wanted generics since the start. It was always a problem implementing them without severely hurting compile time and creating compilation bloat. Rust chose to ignore this problem, by relying on LLVM backend for optimizations and dead code elimination.
-
Are you a real programmer if you use VS Code? No Says OP in the byte sized drama
Hold up, did the members actually push this forward or was support just often memed about and suddenly this proposal was made: https://github.com/golang/proposal/blob/master/design/43651-type-parameters.md
-
Major standard library changes in Go 1.20
As far as I can tell, the consensus for generics was "it will happen, but we really want to get this right, and it's taking time."
I know some people did the knee-jerk attacks like "Go sucks, it should have had generics long ago" or "Go is fine, it doesn't need generics". I don't think we ever needed to take those attitudes seriously.
> Will error handling be overhauled or not?
Error handling is a thorny issue. It's the biggest complaint people have about Go, but I don't think that exceptions are obviously better, and the discriminated unions that power errors in Rust and some other languages are conspicuously absent from Go. So you end up with a bunch of different proposals for Go error handling that are either too radical or little more than syntactic sugar. The syntactic sugar proposals leave much to be desired. It looks like people are slowly grinding through these proposals until one is found with the right balance to it.
I honestly don't know what kind of changes to error handling would appear in Go 2 if/when it lands, and I think the only reasonable answer right now is "wait and find out". You can see a more reasonable proposal here:
https://github.com/golang/proposal/blob/master/design/go2dra...
Characterizing it as a "lack of vision" does not seem fair here--I started using Rust back in the days when boxed pointers had ~ on them, and it seemed like it took Rust a lot of iterations to get to the current design. Which is fine. I am also never quite sure what is going to get added to future versions of C#.
I am also not quite sure why Go gets so much hate on Hacker News--as far as I can tell, people have more or less given up on criticizing Java and C# (it's not like they've ossified), and C++ is enough of a dumpster fire that it seems gauche to point it out.
-
Go's Future v2 and Go's Versioning
There will almost certainly not be a Go 2 in that sense. There is a Go 2 transition doc which extensively discusses what "Go 2" means. The conclusion is
-
What's the status of the various "Go 2" proposals?
As it says on that page - those were not proposals. They were draft ideas to get feedback on. You can see the list of proposals in this repository: https://github.com/golang/proposal
-
An alternative memory limiter for Go based on GC tuning and request throttling
Approximately a year ago we faced with a necessity of limiting Go runtime memory consumption and started work on our own memory limiter. At the same time, Michael Knyszek published his well-known proposal. Now we have our own implementation quite similar to what has been released in 1.18, but there are two key differences:
What are some alternatives?
zio-prelude - A lightweight, distinctly Scala take on functional abstractions, with tight ZIO integration
go - The Go programming language
Discord-Tools - VSCode extension allowing the integration of a Discord chat, bot templates, snippets, themes and more!
thiserror - derive(Error) for struct and enum error types
awesome-vscode - 🎨 A curated list of delightful VS Code packages and resources.
go_chainable - With generics, allowing chainable .Map(func(...)).Reduce(func(...)) syntax in go
trojan-source - Trojan Source: Invisible Vulnerabilities
avendish - declarative polyamorous cross-system intermedia objects
vscode-javascript-extensions - Example VS Code extensions written in JavaScript
functional-go - This library is inspired by functional programming - Clojure
Nim - Nim is a statically typed compiled systems programming language. It combines successful concepts from mature languages like Python, Ada and Modula. Its design focuses on efficiency, expressiveness, and elegance (in that order of priority).
go-generic-optional - Implementation of Optionals in Go using Generics