[ruby-core:42546] [ruby-trunk - Feature #1275][Rejected] IPAddr unnecessarily destroys information on creation

Issue #1275 has been updated by Yusuke Endoh.

Status changed from Assigned to Rejected

I'm rejecting this feature ticket because no progress has been
made for a long time.  See [ruby-core:42391].



I'm not sure if this use case is valid for IPAddr library.
But if you still want the feature seriously, it might be good
to start with creating a patch, as Yugui said.

-- 
Yusuke Endoh <[e-mail]>
----------------------------------------
Feature #1275: IPAddr unnecessarily destroys information on creation
https://bugs.ruby-lang.org/issues/1275

Author: Christopher Smith
Status: Rejected
Priority: Normal
Assignee: Akinori MUSHA
Category: lib
Target version: 2.0.0


=begin
 The IPAddr class internally stores both a complete IP address and a network mask.  For many applications, client code needs to be able to track an interface's IP address (say, 10.253.0.20) and its netmask (/24), and in IPv6, both the 128-bit identifier and the netmask are generally considered part of the address.
 
 The current implementation of IPAddr immediately clears all masked bits, making it impossible to store information like "10.253.0.20/24"; instead, the class stores only the *network* address of 10.253.0.0/24.
 
 Since it is always possible to mask off bits later, IPAddr should internally store the entire address alongside the netmask and provide the masked address on request (as already provided in #mask).  I suggest adding an option "mask_host_part=true" to initialize and changing the check condition at 483 to "if prefixlen and mask_host_part" (to keep from breaking current code).
=end



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