Re: [Discussion] Native - Dropping exceptions from Region::getAll

2017-10-26 Thread Jacob Barrett
Ok I’m calling this one closed. We are going to drop the exceptions map and change the function to return the entry map only. > On Oct 23, 2017, at 11:53 AM, Mark Hanson wrote: > > +1 for dropping the exceptions map. >> On Oct 23, 2017, at 10:36 AM, Ernest Burghardt wrote: >> >> +1 drop excep

Re: [Discussion] Native - Dropping exceptions from Region::getAll

2017-10-23 Thread Mark Hanson
+1 for dropping the exceptions map. > On Oct 23, 2017, at 10:36 AM, Ernest Burghardt wrote: > > +1 drop exceptions map > > On Mon, Oct 23, 2017 at 10:53 AM, Michael William Dodge > wrote: > >> +1 for dropping the exceptions map for symmetry with the Java API >> >> Sarge >> >>> On 23 Oct, 201

Re: [Discussion] Native - Dropping exceptions from Region::getAll

2017-10-23 Thread Ernest Burghardt
+1 drop exceptions map On Mon, Oct 23, 2017 at 10:53 AM, Michael William Dodge wrote: > +1 for dropping the exceptions map for symmetry with the Java API > > Sarge > > > On 23 Oct, 2017, at 09:32, Jacob Barrett wrote: > > > > As part of our decision to replace all function out variables with re

Re: [Discussion] Native - Dropping exceptions from Region::getAll

2017-10-23 Thread Michael William Dodge
+1 for dropping the exceptions map for symmetry with the Java API Sarge > On 23 Oct, 2017, at 09:32, Jacob Barrett wrote: > > As part of our decision to replace all function out variables with return > values we ran into an interesting function with Region::getAll. That > function had two out v

[Discussion] Native - Dropping exceptions from Region::getAll

2017-10-23 Thread Jacob Barrett
As part of our decision to replace all function out variables with return values we ran into an interesting function with Region::getAll. That function had two out variables, one the map of key/value pairs and another map for key/exception pairs. There are no tests that actually test the key/except