[–] 5 points 7 months ago

cfg_select! looks good. cfg_if! always added so much boilerplate that it rarely reduced complexity, even though it offered a valid solution for when you had a complex condition in one branch and then not() that in the other. It was also annoying that you had to add a dependency for those rare cases.

We did also move away from cfg_if!, though, because IDE tooling would mostly just quit working within the cfg_if! macro call. Will have to see, if that's better with this compiler built-in, or if the IDE tooling gets updated to support that well.

  • source
  • [–] 3 points 7 months ago* (4 children)
    • noticed a twitter/X link at the end
    • AI slop and overworked developers (see the other threads in this post)

    Yeah whatever, I'm not going to spend my time to see which bugs exactly they have all over.

  • source
  • [–] 2 points 7 months ago

    The speed was really noticeable, like when people talk about the higher FPS on a game.

    But I also tried to change some configurations that weren't saved,

    Also I couldn't make the address bar work so that I can click on a folder name and see what is in there. Sometimes I don't have a project or folder open only just a file, and I still want to navigate back on the folders, which I didn't manage to do.

    I don't know it was a bit cursed experience, but I still want to give it another try maybe in a year or so.

  • source
  • parent
  • context
  • [–] 3 points 7 months ago (1 child)

    That’s… very interesting. I’ve been using it for ages and haven’t had those sorts of issues.

    FWIW, it’s more or less just as configurable as VSCode and friends, so there’s probably a setting somewhere you can change to correct the behavior you’re having frustrations with.

  • source
  • parent
  • context
  • [–] 4 points 7 months ago

    Off-topic: The switching between light background for text and dark background for code is stupid and annoying. Either use dark for both, or light for both (so I can apply my custom inverse shader without hurting my eyes or breaking the reading flow). This back and forth switching is almost as stupid as using a background color with middle lightness, which I've also seen.

    This has been irking me for a while, so I decided to randomly whine about it now.


    As for the blog content. It's a weird collection of clippy bugs which covers basically the first half of the blog, then a couple of miri bugs and limitations. Then it finally gets to actual rust compiler stuff which just involves cfg_select (a nice to have) and c_variadic support (ffi use-case). So, IMHO, that title is a bit over the top, and it almost does a disservice to a lot of actual good and interesting work that is being done.

  • source
  • [–] 2 points 7 months ago

    Interesting - I think this minimal solution I actually wouldn't mind, but I'd be concerned about introducing syntax for callers. Keeping it as a private construct in libraries seems fine though.

  • source
  • [–] 1 point 7 months ago

    @onlinepersona Given that this subject was already brought up, and regular people from the project said that their is interest for removing the dependency to github (but not leave it, Microsoft is one of the top contributor), I assume that some people would be willing to help the integration a working prototype.In case you need it:rust-lang.zulipchat.com/

  • source
  • parent
  • context
  • [–] 1 point 7 months ago (1 child)

    Oh really? 🤔 Every project on Github that I've tried to contribute to from outside has been resistant to it. But maybe I could give cargo.io a try. Zulip you say? Interesting choice... requires creating yet another account since it doesn't seem to be federated...

  • source
  • parent
  • context
  • [–] [S] 2 points 7 months ago* (last edited 7 months ago)
    view more: ‹ prev next ›