Why cant you initialize BinaryFloatingPoint from BinaryInteger?

taylorswift · 2018-01-01T21:58:50.000Z

title says it all,, this is kind of annoying when writing some generic
FloatingPoint code where both the integral and floating parameters are
unfixed.

xwu · 2018-01-02T01:01:25.000Z

This would be a good addition to the BinaryFloatingPoint protocol. It's not
difficult to implement; it's not present (afaict) simply because
BinaryFloatingPoint was designed before BinaryInteger existed.

···

On Mon, Jan 1, 2018 at 3:58 PM, Kelvin Ma via swift-evolution < swift-evolution@swift.org> wrote:

title says it all,, this is kind of annoying when writing some generic
FloatingPoint code where both the integral and floating parameters are
unfixed.

_______________________________________________
swift-evolution mailing list
swift-evolution@swift.org
https://lists.swift.org/mailman/listinfo/swift-evolution

nnnnnnnn · 2018-01-05T18:01:31.000Z

Right, SE-0067 included that initializer with the caveat that implementation wouldn't be possible until the integer protocols were revised. As far as I can see, that makes this a fix that wouldn't need further SE discussion. (The generic init(exactly:) needs an implementation, too.)

github.com

apple/swift-evolution/blob/main/proposals/0067-floating-point-protocols.md

# Enhanced Floating Point Protocols

* Proposal: [SE-0067](0067-floating-point-protocols.md)
* Author: [Stephen Canon](https://github.com/stephentyrone)
* Review Manager: [Chris Lattner](https://github.com/lattner)
* Status: **Implemented (Swift 3)**
* Decision Notes: [Rationale](https://forums.swift.org/t/accepted-se-0067-enhanced-floating-point-protocols/2420)
* Implementation: [apple/swift#2453](https://github.com/apple/swift/pull/2453)
* Previous Revision: [1](https://github.com/apple/swift-evolution/blob/fb1368a6a5474f57aa8f1846b5355d18753098f3/proposals/0067-floating-point-protocols.md)

## Introduction

The current FloatingPoint protocol is quite limited, and provides only a small
subset of the features expected of an IEEE 754 conforming type.  This proposal
expands the protocol to cover most of the expected basic operations, and adds
a second protocol, BinaryFloatingPoint, that provides a number of useful tools
for generic programming with the most commonly used types.

Revision 2 reintroduces some of the details of the `Arithmetic` protocol from
earlier drafts of this proposal, but as methods in the `FloatingPoint` API,

This file has been truncated. show original

Nate

···

On Jan 1, 2018, at 7:01 PM, Xiaodi Wu via swift-evolution <swift-evolution@swift.org> wrote:

This would be a good addition to the BinaryFloatingPoint protocol. It's not difficult to implement; it's not present (afaict) simply because BinaryFloatingPoint was designed before BinaryInteger existed.

On Mon, Jan 1, 2018 at 3:58 PM, Kelvin Ma via swift-evolution <swift-evolution@swift.org> wrote:
title says it all,, this is kind of annoying when writing some generic FloatingPoint code where both the integral and floating parameters are unfixed.

_______________________________________________
swift-evolution mailing list
swift-evolution@swift.org
https://lists.swift.org/mailman/listinfo/swift-evolution

_______________________________________________
swift-evolution mailing list
swift-evolution@swift.org
https://lists.swift.org/mailman/listinfo/swift-evolution