From: eregontp@...
Date: 2014-11-08T20:39:43+00:00
Subject: [ruby-core:66146] [ruby-trunk - Feature #3067] [Closed] complex.c : Question: why Complex#~ is disabled? It's in the doc

Issue #3067 has been updated by Benoit Daloze.

Status changed from Assigned to Closed

I see, it's from https://gcc.gnu.org/onlinedocs/gcc/Complex.html.
As said before, this is potentially confusing so the current behavior of not defining it seems best.

----------------------------------------
Feature #3067: complex.c : Question: why Complex#~ is disabled? It's in the doc
https://bugs.ruby-lang.org/issues/3067#change-49849

* Author: Benoit Daloze
* Status: Closed
* Priority: Normal
* Assignee: Yukihiro Matsumoto
* Category: core
* Target version: next minor
----------------------------------------
=begin
 Hi, this is more of a question than a bug, feature or whatever,
   but I wonder why Complex#~ has been removed ?
 
 I can read in complex.c:
 #if 0
     rb_define_method(rb_cComplex, "~", nucomp_conj, 0); /* gcc */
 #endif
 
 gcc would have problems with it? why?
 
 Fixnum#~ and Bignum#~ are not commented and work right.
 
 Maybe the method should be added at a higher level, if possible, if it is a compiler issue ?
 
 B.D.
=end




-- 
https://bugs.ruby-lang.org/