SDS
vscode-gitlens
Our great sponsors
SDS | vscode-gitlens | |
---|---|---|
48 | 19 | |
4,787 | 8,747 | |
- | 1.3% | |
0.0 | 9.9 | |
7 months ago | 7 days ago | |
C | TypeScript | |
BSD 2-clause "Simplified" License | 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.
SDS
-
Strlcpy and strlcat added to glibc 2.38
Let me reframe this. What we're saying to do is stop using C string manipulation such as strcat, strcpy, etc. Particularly, I'm saying simply don't use C-style null terminated strings until you actually go to call a C ABI interface where it is necessary.
The argument against this is that you might call something that already does this. Yes, sure, that IS true, but what this betrays is the fact that you have to deal with that regardless of whether or not you add additional error-prone C string manipulation code on top of having to worry about memory ownership, mutation, etc. when passing blobs of memory to "untrusted" APIs.
It's not about passing the buck. Passing a blob of memory to an API that might do horrible things not defined by an API contract is not safe if you do strcat to construct the string or you clone it out of an std::string or you marshal it from Go or Rust. It's about not creating a bigger mess than you already have.
Okay fine, but what if someone hates C++ and Rust and Go and Zig? No problem. There are a slew of options for C that can all handle safer, less error-prone string manipulation, including interoperability with null-terminated C strings. Like this one used in Redis:
https://github.com/antirez/sds
And on top of everything else, it's quite ergonomic, so it seems silly to not consider it.
This entire line of thinking deeply reminds me of Technology Connection's video The LED Traffic Light and the Danger of "But Sometimes!".
https://youtube.com/watch?v=GiYO1TObNz8
I think hypothetically you can construct some scenarios where not using C strings for string manipulation requires more care, but justifying error prone C string manipulation with "well, I might call something that might do something unreasonable" as if that isn't still your problem regardless of how you get there makes zero sense to me.
And besides, these hypothetical incorrect APIs would crash horrifically on the DS9K anyways.
-
Safest way to copy a string?
Even better, use a string handling library. Personally I am a big fan of (sds)[https://github.com/antirez/sds] from the Redis creator. It's not even a dependancy you can just copy the .c and .h to your project.
-
New C features in GCC 13
One nice application is length-prefixed string literals to complement dynamic string libraries:
-
Strlcpy and Strlcat – Consistent, Safe, String Copy and Concatenation (1999) [pdf]
The better answer would be to add data types like SDS[0] to the standard library, and use them as ADTs (Abstract Data Types) [1].
Unfortunely WG14 has proven in 30 years of existence, that it isn't something that they care to fix, and while 3rd party solutions exist, without vocabulary types on the stardard library adoption will never take off.
[0] - https://github.com/antirez/sds
[1] - https://en.wikipedia.org/wiki/Abstract_data_type
-
C Strings and my slow descent to madness
With the woes of string.h being known, why not just use an alternative like https://github.com/antirez/sds ?
I’ve also been having a blast with C because writing C feels like being a god! But the biggest thing that I like about C is that the world is sort of written on it!
Just yesterday I needed to parse a JSON… found a bunch of libraries that do that and just picked one that I liked the API.
-
How can i know for sure that i am allocating enough memory?
Please note that the discussion started with requirement for no dynamic allocation in critical code what virtually eliminates std::string. I agree that std::string code tends to be simpler but the main reason is that the standard C library sucks on strings. There are better alternatives like sds but they are ... not standard.
-
str_header.h - A single header C string library
Another day, another post about a writing a bespoke string lib instead of using SDS
-
C_dictionary: A simple dynamically typed and sized hashmap in C - feedback welcome
d) everything being a macro seems overkill for me (and possibly dangerous, see b)). Maybe implement more as static inline functions, see the sds header: https://github.com/antirez/sds/blob/master/sds.h (which does a similar thing with the header struct).
-
Updated book to learn C
For example, you can use the C language with sds strings (see https://github.com/antirez/sds) if you want to have an easier time with string formatting and don't want to worry about using the famously unsafe string.h functions correctly. You'll still program in ISO C, but just not in the standard library. The same applies to pretty much all parts of the standard library, the only part unsurpassed is pretty much just printf and the math headers (math.h, fenv.h, tgmath.h, complex.h) imo, and the occasional call to exit. A good place to look for libraries if you want to go that route is the awesome-c collection: https://github.com/oz123/awesome-c
-
Convenient Containers: A usability-oriented generic container library
One way around this problem is to declare the container as a pointer to the element type and then store the container’s metadata, alongside its elements, in the heap block to which the pointer points. This approach is already used for dynamic arrays in several container libraries, most notably stb_ds and sds. They place the metadata before the elements and provide the user with a pointer to the elements themselves (this has the nice effect that users can use the [] operator to access elements).
vscode-gitlens
- The Loneliness of the Mid-Level Vimmer
-
Why Git Is Hard
IntelliJ: https://www.jetbrains.com/help/idea/investigate-changes.html
VSCode:
https://marketplace.visualstudio.com/items?itemName=mhutchie...
or https://github.com/gitkraken/vscode-gitlens#commit-graph-
SourceTree: https://confluence.atlassian.com/sourcetreekb/viewing-log-hi...
-
Came back to Git Graph after several months of using GitLens+
Quite a while ago, the GitLens+ plugin gained the Commit Graph feature--the same graph you see in GitKraken. Until then I had used Git Graph for visualizing my repositories and GitLens+ for git blame in the GUI. Since one plugin could now do both, the natural course of action was to remove the other--goodbye, Git Graph!
-
Why I love GitLens in my VsCode - Part 1
Btw, today I want to speak about something different, I love git and I love terminal, but sometimes I love having the info visualised appealingly and get info about the source control quickly. I work with VsCode typically, so some months ago I tried to find a solution for this editor that resolves what was said before. After googling and some testing, the result of my search was: GitLens. Now, I want to show you how it works and how it can improve your routine. So don't waste time and let's jump in it!
-
Both are good, what would you pick?
GitLens extension chef's kiss
-
tig blame online
for GitLens https://gitlens.amod.io/
- GitLens adds “Premium Features” and enough reminders that you don't miss them
-
The Myth of Self-Documenting Code
The better version is to have something like gitlens installed into your IDE and have it dynamically render those git comments.
https://github.com/Axosoft/vscode-gitlens#current-line-blame...
-
where add.
I learned the cli first, but I do use vscode's git integration for staging and committing. I also love gitlens's "commits by file / line" feature.
-
Replacing GitKraken
Hi. Vs code is pretty well integrated with git. There are built in git support and a couple other plugins. For example, the most popular git plugin for vs code is git lens. It also has powerful rebase editor (i guess, it is my favorite feature), which you can enable by following this guide. I personally realy enjoing Git Graph extension, which allow you to observe your git history in pretty similar to git kraken way. It also provide navigation facilities and some other useful features.
What are some alternatives?
Better String - The Better String Library
vscode-jupyter - VS Code Jupyter extension
Experimental Boost.MSM-lite - Boost.SML (formerly called Boost.MSM-lite)
vscode-emacs-mcx - Awesome Emacs Keymap - VSCode emacs keybinding with multi cursor support
libcpuid - a small C library for x86 CPU detection and feature extraction
linux - Linux kernel source tree
ZXing - ZXing ("Zebra Crossing") barcode scanning library for Java, Android
Git - Git Source Code Mirror - This is a publish-only repository but pull requests can be turned into patches to the mailing list via GitGitGadget (https://gitgitgadget.github.io/). Please follow Documentation/SubmittingPatches procedure for any of your improvements.
safestringlib
CodeMaid - CodeMaid is an open source Visual Studio extension to cleanup and simplify our C#, C++, F#, VB, PHP, PowerShell, JSON, XAML, XML, ASP, HTML, CSS, LESS, SCSS, JavaScript and TypeScript coding.
stb - stb single-file public domain libraries for C/C++
gitui - Blazing 💥 fast terminal-ui for git written in rust 🦀