Certainly a good idea, but I'm not really happy with this in its current form.

• I'd like it to work on saved files, too, with their proper names, only going via stdin if &modified.

• This leaves behind in the working directory a binary stdin~; it should be removed (I don't understand why rust run leaves it around, to be frank)

• /dev/stdin isn't cross-platform. It should be using - which rust run... supports in concept as "stdin", but breaks on in linking. TODO: file bug about that (going to bed now). We're probably best to bypass rust run and invoke rustc and the resulting file directly: You could do something along the lines of:

  let s:tempname = tempname()
  exec "!rustc - -o " . s:tempname
  exec "%!" . s:tempname
  unlet s:tempname
  

  Actually, on second thoughts, tempname() might not be such a good idea—the working directory will still be right, but the binary directory wouldn't be, which could potentially cause trouble for some code. Could go for a name like ./.vim-rust-run-binary, I guess. Oh, and on Windows it'll need to end in .exe.

• It'd be kinda nifty if it tied into the rustc compiler (which would need some modification to fit with it, to support a -o X option at least), so that you'd replace the :!rustc step with :make, with the effect that compile errors would be handled normally. (Danger there: it would at present then try to show you the errors in a buffer with the filename <anon>. I guess adding another set of errorformat lines before the others with the hardcoded would more or less fix that up, though if you use other files it would still get hairy.)

What do you think?

@chris-morgan @dotdash any update on this? it has been languishing in the queue for a while. I'm happy to just rubber stamp it, but the concerns are valid.

I'll probably not get around to fix this any time soon. I'll be happy if anyone picks this up, but would not like to see it merged as is, especially, but not only, because of the annoying stdin~ executable it currently leaves behind, which I initially had no idea where it was coming from.

I'm going to close this; if anyone wants to fix it, they can reopen it or submit a new PR :-)