Re:Why did we choose Rust to develop TiKV?
by alexnewman on Wednesday September 27, 2017 @11:29AM
(#15348767)
Go doc and go fmt have rust equivalents. What’s better at profiling?
[ Parent
| on HN ]
Re:Why did we choose Rust to develop TiKV?
by Thaxll on Wednesday September 27, 2017 @11:40AM
(#15348906)
There is nothing out of the box for profiling ( but it's bit different since no GC and use C/C++ tools ).
What's the equivalent of doc godoc -http=:6060 ( it sounds silly by last time I was in a plane and was able to browse the Go doc Like if I had internet access )
Re:Why did we choose Rust to develop TiKV?
by steveklabnik on Wednesday September 27, 2017 @11:58AM
(#15349097)
Just cargo doc; I think it has a --open flag too. (Rust docs don't need a web server running)
Re:Why did we choose Rust to develop TiKV?
by dullgiulio on Wednesday September 27, 2017 @03:51PM
(#15351626)
Probably opens a "file://..." then. Go docs run their own embedded server, they don't need one, just to be precise.
Re:Why did we choose Rust to develop TiKV?
by steveklabnik on Wednesday September 27, 2017 @04:18PM
(#15351890)
Yeah, that's exactly what it does.
Re:Why did we choose Rust to develop TiKV?
by alexnewman on Wednesday September 27, 2017 @12:40PM
(#15349572)
Total nonsense rust makes it trivial to profile