09:57 <nakilon> current state of docs is awful

09:58 <nakilon> how do I find the rdoc fornat description? I google and visit a hundred of links, and there is no format descriotion

09:58 <nakilon> even within several click from https://ruby.github.io/rdoc/index.html

09:59 <nakilon> '# @return [Array]' -- is this rdoc? where is it documented?

10:04 <nakilon> hm, I guess it's yard

10:30 <nakilon> adam12: so cool, the page https://www.rubydoc.info/gems/yard/file/docs/Tags.md#abstract has some HTML trash, but your docs are fine https://gemdocs.org/gems/yard/0.9.37/file.Tags.html#abstract

10:34 <nakilon> I wonder is there is a way to mark as 'abstract' but that has the default implementation

10:35 <nakilon> i.e. the parent class/module does just 'def f x ; x ; end' and you are supposed to override only if your derived class needs it

10:36 <nakilon> so the reader of parent class/module docs won't decide to delete or go around that method

10:52 <CalimeroTeknik> havenwood, pardon my follow-up being so late; adding "Gem::Specification.each { |spec| gem spec.name, spec.version }" to the Gemfile did not do what I had in mind (I managed an equivalent result by simply removing `require 'rubygems'\nrequire 'bundler/setup'` everywhere); what I'm trying to achieve is restore the older bundler behaviour of not installing copies of system gems (already installed system-wide)

11:58 <CalimeroTeknik> maybe `Gem::Specification.each { |spec| gem spec.name, spec.version }` could be adapted for Gemfile.lock though

11:59 <CalimeroTeknik> "use whatever version of anything that happens to be installed"

12:47 <adam12> nakilon: Weird. No idea why they differ, tho the rubydoc.info implementation supports custom YARD plugins and I intentionally didn't, since I do still want to switch to RDoc eventually.

13:03 <nakilon> I wish extend had the analogue of prepend as it is for include

13:06 <nakilon> adam12: new docs design is awful

13:07 <nakilon> humankind has agreed for 10 years already that the "let us add 5 times more whitespace between lines" is a bad practice that has killed several google projects, and yet makes of new design are like living under a rock and willing to do the same fiasco

13:07 <nakilon> with the same font size you get half of information on screen, it's just unreadable

13:28 <adam12> I don't mind it, tho I'd maybe reduce padding between method head and the description of that method..

13:28 <adam12> I wish that we hired a designer to improve it tho.

13:30 <nakilon> (about extend; probably it's `singleton_class.prepend`)

13:30 <nakilon> just leave old styles

13:31 <nakilon> yard looks even nicer

13:32 <nakilon> this huge line spacing is to consume people's time when they are on phone