GitLab now enforces expiry dates on tokens that originally had no set expiration date. Those tokens were given an expiration date of one year later. Please review your personal access tokens, project access tokens, and group access tokens to ensure you are aware of upcoming expirations. Administrators of GitLab can find more information on how to identify and mitigate interruption in our documentation.
Undo some changes from !248 that are no longer needed
It turns out these were only needed before I moved the vectorization of the RNGBase objects to the right place. The vectorized C printer does actually print scalar code when it is passed scalar variables and field accesses.
