1. 14
  1.  

  2. 3

    I haven’t thought in detail about what should be public versus what the compiler insists has to be public due to how I’m using these modules. I think for a command-line application it doesn’t matter so much what my public API is because no one will be consuming it, but for a library it’s probably important. I will come back to these considerations later and see if I can understand how to manage separation of concerns in rust in more detail.

    The simplest way to manage it is by just slapping pub(crate) on everything that you aren’t 100% sure you want exposed. It makes the item public to the whole crate, but public to other crates.

    1. 2

      If anyone with firefox on a mac or with hugo experience can help me fix whatever is causing the syntax highlighted code blocks to not render correctly on some browsers I’d really appreciate it

      Apparently some people are seeing the code blocks like this: https://imgur.com/a/ARqo9qD

      1. 1

        FF on macOS: the code blocks seem to render fine for me…

        1. 1

          Fine for me on Firefox 67.0.2 on Mac OS 10.13.6 too. It’s not some dark mode thing is it?

          1. 1

            I do have the problem in the screenshot, and I’m using dark mode, but switching to light mode didn’t fix it.

            Comparing Firefox against Chrome I can see what it’s supposed to look like, but I can’t see from the element inspector why Firefox is getting it wrong.

          2. 1

            Came to say same, on FF on macOS and the code blocks are rendering almost black on black, I tried popping open dev tools and changing the colour to white, but after a second all the text on the page went white, then came back and then the code blocks reverted, so you’ve got some JavaScript loaded there that either FF is screwing up running or the script itself has some issues.

            1. 1

              I think I’m going to change the theme, the one I’m using appears to be unmaintained.