bug#19232: 25.0.50; ring.el: why not autoload `ring-member' etc.?

bug#19232: 25.0.50; ring.el: why not autoload `ring-member' etc.?

[Drew Adams]

Subject line says it all.  Why make users `require' ring.el for such
functions, or autoload them themselves?  Do what you do now for `ringp'
and `make-ring' for other functions as well, such as `ring-insert',
`ring-member', and `ring-next'.  This is a utility library.

In GNU Emacs 25.0.50.1 (i686-pc-mingw32)
 of 2014-10-20 on LEG570
Bzr revision: 118168 rgm@gnu.org-20141020195941-icp42t8ttcnud09g
Windowing system distributor `Microsoft Corp.', version 6.1.7601
Configured using:
 `configure --enable-checking=yes,glyphs CPPFLAGS=-DGLYPH_DEBUG=1'

bug#19232: 25.0.50; ring.el: why not autoload `ring-member' etc.?

[Stefan Monnier]

tags 19232 notabug
thanks

> Subject line says it all.  Why make users `require' ring.el for such
> functions, or autoload them themselves?  Do what you do now for `ringp'
> and `make-ring' for other functions as well, such as `ring-insert',
> `ring-member', and `ring-next'.  This is a utility library.

I think the error is to autoload ring-p and make-ring.  Of course it's
a bit late to fix it, but that's no reason to add many more autoloads.
Just (require 'ring) like everyone else if you use functions from that
library.


        Stefan