Hey Tom,

Well, I could change the setting to "anyone with the link can edit" - we 
risk vandalism in that case, but as long as we keep the document link to 
here the risk is minimal.

On Friday, 31 July 2015 15:43:06 UTC+2, Tom Breloff wrote:
>
> I added some info to the readme at https://github.com/tbreloff/Unums.jl.  
> I talk a little bit about how I'm intending to build the package, the 
> available types, etc.  There is also a stub issue for continuing the 
> discussion of how unums fit into the world of numerical analysis: 
> https://github.com/tbreloff/Unums.jl/issues/2.  I'd love collaboration 
> from anyone that wants to help implement some of the conversion functions 
> and operations.  I don't claim to be an authority on floating point 
> arithmetic, so any and all comments are welcome.
>
> Job: Any chance you can move your google doc to a wiki or something more 
> accessible?  I'm happy to include it in my package if you want.
>
> On Thu, Jul 30, 2015 at 6:51 PM, Job van der Zwan <j.l.van...@gmail.com 
> <javascript:>> wrote:
>
>> On Thursday, 30 July 2015 00:33:52 UTC+2, Job van der Zwan wrote:
>>>
>>> BTW, Tom, I was already working on a summary of the book (on an IJulia 
>>> notebook). I'm on mobile right now so don't have access to it, but I can 
>>> share it later. I think something like that might be useful to attract more 
>>> collaborators - we can't expect everyone to read it.
>>
>>
>> Ok, so since Tom is already working on a package, I moved my 
>> summary-in-progress to Google Drive where it's easier for people to leave 
>> comments:
>>
>>
>> https://docs.google.com/document/d/1d36_ppKeZDuYRadLm9-Ty8Ai2XZE5MS5bwIuEKBJ1WE/edit?usp=sharing
>>  
>>
>> For others who have read the book, please correct any errors or 
>> misunderstandings on my part that you see. Expanding sections is also 
>> encouraged :P
>>
>> Right now it's very bare-bones (since the meat is what you *can do* with 
>> unums, not the definition of the format itself), but I'll hopefully get 
>> around to expanding it a bit in the coming weeks.
>>
>
>

Reply via email to