Make it strongly statically typed. Dictionaries and lists must have all their items of the same type. For extra confusion.
Make it strongly statically typed. Dictionaries and lists must have all their items of the same type. For extra confusion.
Honestly, I didn’t even consider this as possible. I’m saving the post in case I’m very bored and want to do it.
Any editor that support LSP has the same (or better) auto complete. All IDEs also have the same (or better) auto complete, don’t even need LSP.
I meant native as in non-web. There are plenty of cross-platform GUI toolkits out there that don’t use JavaScript. Some of them native-looking even. But more than the looks, it’s about performance.
I feel like browser support is such a niche. I don’t understand why many IDEs dedicate so many resources to make it work on the browser. There are already many options to code on the web if you need it.
Why would they copy VSCode including the aspect people hate most.
Had they made it in a native gui I might actually consider it. Otherwise, why wouldn’t I just choose vscode.
This synthetic benchmark is nice a general wisdom thing. But I’d love a more complete analysis taking into account loading from memory, caches, SIMD, CPU pipeline and all of that.
Probably when taking all those things into account (specially loading values from memory) the performance difference of a div and a mult should be negligible.
Docs should be written for someone experienced in programming but inexperienced with the API. If it is about a niche subject (for example VR).
Whenever an explanation contains something about that niche subject, you don’t need to explain everything, but maybe provide a link towards another place (for example wikipedia) that explains it.
Untyped function definitions + *args + *kwargs + args that can be of many types + strings used as enums don’t help. The language that imo needs the most documentation is at the same time the one that lacks it the most.
You don’t need to have wired across the room. You can put them through the wall like every other cable. If the wire tubes are not full, it isn’t very complicated. I put my Ethernet wires in the wall.
Why not respond with the appropriate HTTP Code, and then also put the same code in the json?
Why do ISPs rotate IPv6 prefixes? Aren’t they basically infinite?
The main reason I want IPv6 is so I don’t have to use fancy DNS for dynamic addresses.
I unironically do this. There was one update that wiped one guy’s Documents/Downloads/Images/Videos. So I made my own and store my things there.
Not always possible. In Spain IPv6 adoption is at like 5%. There’s literally no ISP that offers it. I don’t even know how that 5% got it, maybe special deals.
If you mean lambdas like in python where you say lambda x: x+1
, they are called closure
s in rust, try searching for that instead.
Well, of course you can have few indent levels by just not indenting, I don’t think the readability loss is worth it though. If I had give up some indentation, I’d probably not indent the impl {} blocks.
Why have an async block spanning the whole function when you can mark the function as async? That’s 1 less level of indentation. Also, this quite is unusable for rust. A single match statement inside a function inside an impl is already 4 levels of indentation.
Both RefCell and unsafe are features of the language. That’s like saying python’s OOP sucks if you don’t use the class
keyword.
I don’t have the data, but I don’t think it’s wild to assume that most rust programs have 0-1 unsafe blocks, in total. Except for special cases like ffi.
Even if your rust project has 1000s of unsafe blocks, it is still safer than C++, which is 100% an unsafe block. You only have to carefully review the parts marked “unsafe”, in C++ you have to carefully review the whole code.
Also, because unsafe blocks are explicitly declared, you know which parts of the code require extra carefulness, and if you encounter a memory bug, doing Ctrl+F “unsafe” will soon show the root cause.
Inline comments yes.
Function/Class/Module doc comments should absolutely explain “what”.