hvenev (u/hvenev) - Readit News

It’s OK to block ads (2015)blog.practicalethics.ox.a...

hvenev commented on C3 solved memory lifetimes with scopes c3-lang.org/blog/forget-b... · Posted by u/lerno

hvenev · a month ago

I'm struggling to understand how this has anything to do with borrow checking. Borrow checking is a way to reason about aliasing, which doesn't seem to be a concern here.

This post is about memory management and doesn't seem to be concerned much about safety in any way. In C3, does anything prevent me from doing this:

  fn int* example(int input)
  {
      @pool()
      {
          int* temp_variable = mem::tnew(int);
          *temp_variable = input;
          return temp_variable;
      };
  }

hvenev commented on FP8 is ~100 tflops faster when the kernel name has "cutlass" in it twitter.com/cis_female/st... · Posted by u/limoce

hvenev · a month ago

In `libnvidia-nvvm.so` the string `cutlass` appears right after `Memory Dependence Analysis` and `memdep`. Perhaps it acts as an optimization attribute of some sort, where the compiler is allowed to make assumptions about the kernel's behavior that are not valid in general?

hvenev commented on What is going on in Unix with errno's limited nature utcc.utoronto.ca/~cks/spa... · Posted by u/ingve

o11c · 2 months ago

`openat` has basically solved that since 2.6.16 (which came out in 2006). There are still some uncommon APIs have been slow to gain `at` variants but there's usually a workaround (for example, `getxattrat` and family were only added in 6.13 (this January), but can be implemented in terms of `openat` + `fgetxattr`)

hvenev · 2 months ago

> can be implemented in terms of `openat` + `fgetxattr`

Except for symlinks. `fgetxattr` requires a file opened for read or write, but symlinks can only be opened as `O_PATH`.

hvenev commented on Old Soviet Venus descent craft nearing Earth reentry leonarddavid.com/old-sovi... · Posted by u/Wingman4l7

af78 · 4 months ago

May 9th is in that range. My goodness, how ironic it would be if it hit the parade in Moscow...

hvenev · 4 months ago

Sadly the inclination of the orbit prevents it from falling that far north.

hvenev commented on Darcs, Friendly Version Control darcsbook.acmelabs.space/... · Posted by u/tusslewake

JTyQZSnP3cQGa8B · 6 months ago

> Is the world a better place now?

Don't ask me because the only SCM I have been using for the past 15 year is git and I hate it. Every company uses it, I made a lot of PowerPoint presentations to teach people how to use it, yet I refuse to use its command-line.

I switched from SourceSafe/SVN/Mercurial to git, but never used Darcs. IMHO git is fine as an assembly language of SCM, but I'm trying to switch to jujutsu which has a better CLI while staying compatible with git as a backend.

hvenev · 6 months ago

I think git is quite nice and easy to work with once you realize one thing: git is first and foremost a filesystem. Version control is built on top.

hvenev commented on VSCode’s SSH agent is bananas fly.io/blog/vscode-ssh-wt... · Posted by u/zdyxry

hvenev · 7 months ago

For local communication Microsoft Visual Studio Code often uses TCP sockets (bound to localhost) even though UNIX sockets are available. What's more, old versions used to pass the authentication token as a command-line argument, exposing it to all users on the system.

I wonder how many other security disasters it contains that nobody has discovered yet.

hvenev commented on Congo gov. says it's 'on alert' over mystery flu-like disease that killed dozens ctvnews.ca/health/congo-g... · Posted by u/amichail

hvenev · 9 months ago

Despite the sad context, this seems refreshing -- an alert is raised due to a real and serious concern.

hvenev commented on Rust Trademark Policy Updates foundation.rust-lang.org/... · Posted by u/PeterWhittaker

tredre3 · 9 months ago

I don't think we can argue in good faith that those forks are publicly distributing a modified version of the rust programming language, unless they actually publish releases.

hvenev · 9 months ago

I don't know, to me it just seems like a plausible interpretation:

- In GitHub, forks of public repositories are themselves public repositories.

- GitHub repositories can be cloned, which is a form of distribution.

- Therefore any fork that implements, for example, a change to the programming language itself, but still uses the name "Rust", is distributing a modified version of the programming language in a manner that is not allowed.

I sincerely hope that this is not the interpretation taken by the Rust Foundation, but I cannot know for sure. It seems very open to selective enforcement.

hvenev commented on Rust Trademark Policy Updates foundation.rust-lang.org/... · Posted by u/PeterWhittaker

hvenev · 9 months ago

The part of the policy about distributing modified versions of the Rust compiler seems interesting:

> Publicly distributing a modified version of the Rust programming language, compiler, or the Cargo package manager, provided that the modifications are limited to:

> - code adjustments for the purpose of porting to a different platform, architecture, or system, or integrating the software with the packaging system of that platform

It looks like distributing a modified version with any change that isn't related to compatibility with a different platform/architecture/system is not allowed. This would probably make almost all GitHub forks of Rust non-compliant.

u/hvenev

KarmaCake day320April 3, 2019View Original