People sometimes use it for type conversions but that's in line with usage elsewhere, no?
455 karma · joined June 14, 2015
People sometimes use it for type conversions but that's in line with usage elsewhere, no?
I just looked at the Git history and this is plain false. It already looked that way when the big source tree move (src/pkg/ -> src/) was done in 2014. Tracing it back further (to before Go 1.0 times, when there wasn't even a builtin error interface yet and the function returned os.Error), ImportedLibraries was *never* implemented in debug/pe.
Nothing to do with Google here, by the way. It's just the default format of the Unix date command.
So if you can't remember the order, just switch to your shell and run `LC_ALL=C date`.
See for example: https://www.redhat.com/sysadmin/podman-docker-compose
I'm pretty sure that if someone from the University of Minnesota would like to contribute something of value to the Linux kernel, dropping a mail to GregKH will result in that being possible.
Unfortunately, using self-hosted runners to provide additional capabilities not supported by Github-hosted ones is basically impossible (for public repos at least) as you can't restrict a runner to an organization or project. Set up a bare-metal runner and it will receive jobs from random forks.
It's pretty common on Unix-like systems (especially in multi-user environments) and not at all specific to macOS.
References:
https://wiki.archlinux.org/index.php/autofs
https://www.freebsd.org/cgi/man.cgi?query=autofs&sektion=5
https://access.redhat.com/documentation/en-us/red_hat_enterp...
Does this refer to standard Web APIs or Chrome-specific and more or less experimental interfaces?
% taskset 1 nproc
1
% taskset 1 getconf _NPROCESSORS_ONLN
8It's also more general as there are other commonly-needed transformations that have an even weaker case for explicit support in the CSV library (charset conversion, dropping other bogus bytes, ...).
You might be thinking of the HTTP server push functionality. That was introduced with HTTP/2 and has been deployed for years already over TCP transports (i.e. totally unrelated to QUIC).
Due to how advertising networks work, I'd be surprised if anyone used server push in the way you fear.
Instead, you can observe the same thing with many other ecosystems/platforms once they have reached a certain scale. Ask Microsoft's Windows team or the Linux kernel maintainers about the importance of keeping existing programs running. Or maybe the stewards of other programming languages like C or C++ can tell you about the difficulty of evolving a language when you have a gazillion lines of pre-existing code to consider. How long does it take the world to phase out support for obsolete SSL/TLS versions, even in the presence of well-known weaknesses?
It seems to me that the more users something has, the more thought has to be put into how not to break them.
Isn't programming in the large exactly the kind of thing Go set out to tackle? Placing a high value on stability appears only logical then.
> An authorization issue discovered in the CI jobs token handling allowed read access to public projects with restricted repositories. This issue is now mitigated in the latest release and is waiting for a CVE ID to be assigned.
A GitLab project can have multiple repositories? I don't think so. Is this just s/project/group/?
This might have been a factor here, given that most of Gosling's peers back then were probably still more familiar with K&R C and its different set of conversion rules.
Also note that the Zdnet headline seems bogus. Better look at the actual source[1] for their "news" which was posted to HN some time ago.
[1] https://googleprojectzero.blogspot.com/2020/02/mitigations-a...
https://golang.org/src/runtime/map.go
https://golang.org/src/runtime/slice.go
I don't see why you couldn't do something similar in your own Go code. It just won't be as convenient to use as the compiler wouldn't fill in the type information (element size, suitable hash function, etc.) for you. You'd have to pass that yourself or provide type-specific wrappers invoking the unsafe base implementation. More or less like you would do in C, with some extra care to abide by the rules required for unsafe Go code.
I think this results from a misunderstanding of how undefined behaviour works in C. When a program exhibits undefined behaviour it is not a valid C program. The compiler may just assume (instead of having to prove) that it doesn't happen.
Example: the memcpy(3) standard library function. C says the behaviour is undefined if the given areas overlap. That means the implementation can perform optimizations "knowing" that there is no overlap. A valid C program can't possible invoke memcpy with buffers aliasing each other (because then, the program would be invalid). The compiler is not required to issue a diagnostic about these kinds of incorrect programs and just compiles your code assuming they don't exist.