I’m wondering why we don’t use any type and definition-aware IDEs that could render the first line as a proper table (especially once there is a list of items of the same type involved). With headers and aligned fields. Similar to how Word would do it with inline tables.
Ideally of course with a switch to change to the second, more verbose definition.
Depending on compiler flags was implicitly mentioned for sbt, though (point 8). Depending on the `.value` of the `scalaVersion` configuration property is the same thing and can be done for all other settings input as well.
You could in principal store the old history in a separate repository then (reasons for this may be that the repo historically contained many binary files, possibly because it’s been converted from an SVN repo). After refactoring and rebasing (Note: You do in fact change the SHAs in this scenario – what they do in the blog post is a rebase+squash/fixup basically.) you prepare a new repo which is much smaller and in which you do all further development.
However, sometimes it may be necessary for developers to do a `git blame` which needs to include the old data or similar. If this happens, you add the historical repo as another remote and `git replace` the oldest commit from the dev repo with the historical repo.
Only a few developers will ever need to use `git replace` in this scenario, so it would not say that it is too confusing. (If it was confusing, I’d say everybody would probably have learned that it exists the hard way…) Maybe think of it as a kind of git submodule but for time.
For starters, they could try to get the spacing in and between UI elements right. For example, the text in drop down menus looks pretty misaligned in those screenshots.
I find that casually overlooking the root directory very often gives me a good estimate of how active the project is (and in which subdirectories it’s been worked on most recently) and also (very superficially) how clean the code base is (e.g. are there falsely committed backup/swap/a.out files even in the root dir). Of course, in most cases I’d immediately scroll down to the readme.
Unless, however, I really do want to view a file online (say because I want to check the API of some command I’m using and it is not documented otherwise) in which case I really appreciate that it is so easy to find. I really don’t understand why most other web frontends (Bitbucket, Gitweb, GitLab) make the commit log the first thing to see on the summary page. These mean nothing to me from an outside perspective.
round(x) only works for a few specialised types of x. help(round) tells you that it will return the same type then. Of course for a type of MathConst{:π}, that won’t work. For generic types, you need to at least specify the number of digits (round(pi, 3)). (See also: methods(round))
Ideally of course with a switch to change to the second, more verbose definition.