5 ms·

As a haskeller who's now stuck doing mostly nodejs, I've been eagerly watching Rust's development. One thing keeping me from using it is its immaturity and eco

by maxcan 14y ago

As a haskeller who's now stuck doing mostly nodejs, I've been eagerly watching Rust's development. One thing keeping me from using it is its immaturity and ecosystem. Is there any chance of a rustfix tool, akin to Go's gofix tool, being developed to lower the risk of using Rust today? In general, well done guys.

steveklabnik 14y ago
I'm only a big fanboy of Rust, I only have two patches in, and pay more attention than many, but I'm not aware of an existence of rustfix. Personally, I don't think there's enough code 'in the wild' to justify this at the moment. With Go, Google was putting it into production from the first release, no?
- eikenberry 14y ago
  They had it in production before the first release. So yeah.
- maxcan 14y ago
  I know its not there, was wondering if there were any plans. Its very much a chicken and the egg issue with "enough code 'in the wild' to justify this"
  - asb 14y ago
    There's plenty of Rust code out there, even if much of it is in the Rust compiler itself :). I suspect the problem has been that many of the changes have been of a nature that don't make automated fixes easy (or necessarily desirable).
    - pcwalton 14y ago
      Yeah, it's hard to automate the fixes; most of the things gofix was used for is things like adding semicolons and changing method names. That said, I would definitely welcome a rustfix for the easier changes.
mcpherrinm 14y ago
I follow development a bit, but am not yet involved heavily. From what I gather, one of the goals of a 1.0 release is that any subsequent releases will have enough tooling to painlessly upgrade to a new version. Something like a 'rust fix' command is surely how you'd want to implement that. Making such a tool shouldn't be enormously painful, given the infrastructure to pretty-print your code exists in the rust compiler.
pron 14y ago
I would actually prefer a more general fix tool like Java's Jackpot[1] (now also a part of NetBeans[2]), that would allow automatic upgrade of any API, not just those that are part of the language. [1] https://bitbucket.org/jlahoda/jackpot30/wiki/Home https://bitbucket.org/jlahoda/jackpot30/wiki/Home [2] https://netbeans.org/kb/docs/java/editor-inspect-transform.html https://netbeans.org/kb/docs/java/editor-inspect-transform.h...

by maxcan 14y ago

steveklabnik 14y ago

I'm only a big fanboy of Rust, I only have two patches in, and pay more attention than many, but I'm not aware of an existence of rustfix. Personally, I don't think there's enough code 'in the wild' to justify this at the moment. With Go, Google was putting it into production from the first release, no?

eikenberry 14y ago
They had it in production before the first release. So yeah.
maxcan 14y ago
I know its not there, was wondering if there were any plans. Its very much a chicken and the egg issue with "enough code 'in the wild' to justify this"
- asb 14y ago
  There's plenty of Rust code out there, even if much of it is in the Rust compiler itself :). I suspect the problem has been that many of the changes have been of a nature that don't make automated fixes easy (or necessarily desirable).
  - pcwalton 14y ago
    Yeah, it's hard to automate the fixes; most of the things gofix was used for is things like adding semicolons and changing method names. That said, I would definitely welcome a rustfix for the easier changes.

mcpherrinm 14y ago

I follow development a bit, but am not yet involved heavily. From what I gather, one of the goals of a 1.0 release is that any subsequent releases will have enough tooling to painlessly upgrade to a new version. Something like a 'rust fix' command is surely how you'd want to implement that. Making such a tool shouldn't be enormously painful, given the infrastructure to pretty-print your code exists in the rust compiler.

pron 14y ago

I would actually prefer a more general fix tool like Java's Jackpot[1] (now also a part of NetBeans[2]), that would allow automatic upgrade of any API, not just those that are part of the language. [1] https://bitbucket.org/jlahoda/jackpot30/wiki/Home https://bitbucket.org/jlahoda/jackpot30/wiki/Home [2] https://netbeans.org/kb/docs/java/editor-inspect-transform.html https://netbeans.org/kb/docs/java/editor-inspect-transform.h...