ruby.git/include/ruby/backward/2, branch ruby_3_0 The Ruby Programming Language include/ruby/backward/2/rmodule.h: deprecate 2020-08-27T07:42:06+00:00 卜部昌平 shyouhei@ruby-lang.org 2020-07-22T06:37:28+00:00 5ca44076f47dce3a70b5f4755f5195f0f9093fc4 Only one function in only one file uses contents of this public header. That is not a wise idea. Let's just free the header's soul. 
Only one function in only one file uses contents of this public header.
That is not a wise idea.  Let's just free the header's soul.
include/ruby/backward/2/r_cast.h: deprecate 2020-08-27T06:03:36+00:00 卜部昌平 shyouhei@ruby-lang.org 2020-07-22T05:44:25+00:00 cd1d6d90299d727ad4a87c42f3ba09c87df2bce3 Remove all usages of RCAST() so that the header file can be excluded from ruby/ruby.h's dependency. 
Remove all usages of RCAST() so that the header file can be excluded
from ruby/ruby.h's dependency.
improve deprecation warning 2020-08-27T06:02:52+00:00 卜部昌平 shyouhei@ruby-lang.org 2020-07-22T04:02:33+00:00 442525527e2fa052e6d8752adffeaa0855b75ff7 We should not recommend RBIMPL_*. 
We should not recommend RBIMPL_*.
DEPRECATED_TYPE: is deprecated 2020-08-27T06:02:52+00:00 卜部昌平 shyouhei@ruby-lang.org 2020-07-22T01:55:30+00:00 21b3bc10d3626272683e085b2b3ea62d2c05b1d7 Nobody uses this macro any longer. 
Nobody uses this macro any longer.
git rm include/ruby/backward/2/extern.h 2020-08-27T05:07:49+00:00 卜部昌平 shyouhei@ruby-lang.org 2020-07-21T06:22:18+00:00 b2e1688e7d44d45e772ac9d5e79f4ad6e70141d5 






sed -i 's|ruby/impl|ruby/internal|'
2020-05-11T00:24:08+00:00

卜部昌平
shyouhei@ruby-lang.org

2020-05-08T09:31:09+00:00

9e41a75255d15765648279629fd3134cae076398

To fix build failures.





To fix build failures.







sed -i s/ruby3/rbimpl/g
2020-05-11T00:24:08+00:00

卜部昌平
shyouhei@ruby-lang.org

2020-05-04T07:27:48+00:00

122f96c362c0391045d9b10d81d3681cb2455da5












sed -i s/RUBY3/RBIMPL/g
2020-05-11T00:24:08+00:00

卜部昌平
shyouhei@ruby-lang.org

2020-05-04T06:52:56+00:00

97672f669af53c41b094772559030195787406be

Devs do not love "3".  The only exception is RUBY3_KEYWORDS in parse.y,
which seems unrelated to our interests.





Devs do not love "3".  The only exception is RUBY3_KEYWORDS in parse.y,
which seems unrelated to our interests.







sed -i s|ruby/3|ruby/impl|g
2020-05-11T00:24:08+00:00

卜部昌平
shyouhei@ruby-lang.org

2020-05-04T06:35:26+00:00

d7f4d732c199df24620a162372c71ee83ed21e62

This shall fix compile errors.





This shall fix compile errors.







include what you use.
2020-04-13T07:06:00+00:00

卜部昌平
shyouhei@ruby-lang.org

2020-04-12T06:42:45+00:00

c37a357c13b399b79fb1ef197738f60cae472dbf

This reverts commit 443389effc37308ce1a3c3a840082a344fc6af56.
This reverts commit d94960f22ec2de3a3855305cb51343806d2b46c7.

Inclusion of header files must be explicit.  Every file shall directly
include what is necessary.

https://github.com/include-what-you-use/include-what-you-use says:

> When every file includes what it uses, then it is possible to edit any
> file and remove unused headers, without fear of accidentally breaking
> the upwards dependencies of that file. It also becomes easy to
> automatically track and update dependencies in the source code.

Though we don't use iwyu itself, the principle quoted above is a good
thing that we can agree.

Now that include guards were added to every and all of the headers
inside of our project this changeset does not increase compile time, at
least on my machine.





This reverts commit 443389effc37308ce1a3c3a840082a344fc6af56.
This reverts commit d94960f22ec2de3a3855305cb51343806d2b46c7.

Inclusion of header files must be explicit.  Every file shall directly
include what is necessary.

https://github.com/include-what-you-use/include-what-you-use says:

> When every file includes what it uses, then it is possible to edit any
> file and remove unused headers, without fear of accidentally breaking
> the upwards dependencies of that file. It also becomes easy to
> automatically track and update dependencies in the source code.

Though we don't use iwyu itself, the principle quoted above is a good
thing that we can agree.

Now that include guards were added to every and all of the headers
inside of our project this changeset does not increase compile time, at
least on my machine.