Extensions of Futures and Promises tracking #7

dickwall · 2015-08-20T14:19:28Z

https://docs.google.com/document/d/1Vza2-B3FzgtleX8RNs6rqRbhOn9jotrUfFB77h0DIGU/edit?hl=en_US#heading=h.bu8cg3api4vx

Need volunteer to reach out to Anton and Eduard regarding current interest and commitment to this SLIP.

SIP (which would likely become a SLIP) has been dormant for over a year.

dickwall · 2015-09-07T20:19:23Z

Contact info:
https://ua.linkedin.com/in/eduardmaltsev
https://ua.linkedin.com/in/antonkolmakov

dickwall · 2015-09-09T02:53:31Z

Have now reached out to both Eduard and Anton through linked in (the only way I could find to contact them at present). Waiting for any response.

alexandru · 2015-09-11T10:19:26Z

@dickwall found out about this SLIP and I would be interested in contributing. I also have some objections and possible improvements to what's mentioned in that document. To where can I submit them for discussion? Can I do that here?

alexandru · 2015-09-11T10:52:19Z

I've pasted some suggestions based on what I did in a gist, see link.

Cheers,

dickwall · 2015-09-11T21:52:21Z

@alexandru this is a good place to gather those thoughts and notes. I have not yet heard back from Anton or Eduard, so it's possible if you are interested you could volunteer to take the initiative on this?

alexandru · 2015-09-11T22:24:00Z

@dickwall, yes I'm interested, I would like to take this further. Tell me what are the next steps. Should I submit a new or modified document for review?

dickwall · 2015-10-11T19:31:39Z

@alexandru yes please. An updated document would be a great start. Sorry for the delay in responding. If you check out the README.md in scala/slip, that should be good information to get you going in submitting a SLIP pull request if you are so inclined.

dickwall · 2015-11-02T22:56:47Z

@alexandru just checking in on this issue, any developments here?

alexandru · 2016-01-05T01:10:55Z

@dickwall sorry for the silence, I've been very busy, but I'm back. I have started a new project that will showcase where I'd like this to go: https://github.com/monifu/scalax

In particular, in addition to our extensions to Future, I think we also need: Cancelable and Scheduler. The implementations for these already exist in the aforementioned project. And if we introduce the Cancelable and a Scheduler that can trigger timeouts and create delayed future results, it's natural to also have a CancelableFuture, that I'll also like to propose.

Right now me and a colleague are refining the implementation, I'll follow up with a full document.

Cheers,

viktorklang · 2016-07-13T19:24:33Z

@dickwall Is this SLIP still active?

jvican · 2016-07-13T20:00:30Z

Hello Viktor, we have processed it in today SIP's meeting even if it hasn't been active for a while.

I think it would be good to find out whether the authors plan to work on this or not. If they do, it will be one of the first discussion points in the next SLIP Committee this August, and processed under the new SLIP process that will be released soon.

I would recommend the authors to start polishing the design and implementing a proof of concept, and thus speed up the decision process.

viktorklang · 2016-07-13T21:26:47Z

@jvican Yes, a PoC would be much easier to consider and discuss.

jvican · 2016-07-22T14:57:44Z

Hello @alexandru, I will take your previous comments as a confirmation that you will be the new author of this SLIP. Please, correct me if I'm wrong.

This is very likely to be discussed in the next SLIP meeting on 17th August. Also, I'd like to invite @viktorklang as a guest to help us discuss and review this proposal. In order to ensure fruitful discussions, we would need a more concrete design document and a rough implementation (a proof of concept is enough). If you certainly know that you cannot make them before the next meeting, I will reschedule the discussion to the date that you find more appropriate.

alexandru · 2016-07-22T19:47:43Z

OK, I'll be away until the 7th, but I can make the SLIP meeting on the 17th.

alexandru · 2016-07-22T19:48:21Z

BTW, I don't know what that means, please provide details. Is it a Skype/Hangouts meeting?

jvican · 2016-07-22T22:57:53Z

The SLIP committee will have a Hangouts on the 17th August discussing the design of your proposal. It follows the same format as the SIP meetings. Great to hear you'll be able to make it! 😄

viktorklang · 2016-07-23T16:03:39Z

What time?

Cheers,
√

On Jul 23, 2016 00:57, "Jorge" notifications@github.com wrote:

The SLIP committee will have a Hangouts on the 17th August discussing the
design of your proposal. It follows the same format as the SIP meetings.
Great to hear you'll be able to make it! 😄

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
#7 (comment), or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAAqd09n75QXe169IzfFvsfgQq0uvOUCks5qYUrzgaJpZM4FvKcr
.

jvican · 2016-07-23T19:12:13Z

I will send out the details soon to all the attendees, but probably around 5pm in Europe.

alexandru · 2016-08-17T14:43:24Z

Hi guys, is the meeting still today? Haven't received anything.

Not sure what 5 pm Europe means, I can make 5 pm GMT, but sooner than that would be difficult.
I'm also open to rescheduling, for tomorrow, or whatever.

Also, sorry for not sending any document. I've been busy and it is in progress. Will be ready for our meeting and we can do screen sharing or something.

viktorklang · 2016-08-17T14:53:08Z

Unless there's an invite I have no way of tracking these things. I am
unavailable today.

Cheers,
√

On Aug 17, 2016 16:43, "Alexandru Nedelcu" notifications@github.com wrote:

Hi guys, is the meeting still today? Haven't received anything.

Not sure what 5 pm Europe means, I can make 5 pm GMT, but sooner than that
would be difficult.
I'm also open to rescheduling, for tomorrow, or whatever.

Also, sorry for not sending any document. I've been busy and it is in
progress. Will be ready for our meeting and we can do screen sharing or
something.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
#7 (comment), or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAAqdw_a6nTdeMIxCrtpVN2IHfNBZZwVks5qgx4PgaJpZM4FvKcr
.

jvican · 2016-08-17T15:05:35Z

There's no meeting today, it's been delayed until new notice. I'm currently polishing the details of the new process and getting in touch with all the Committee members.

Sorry for the inconvenience.

alexandru · 2016-08-17T15:06:18Z

That's fine, let me know in advance so I can prepare.

Thanks,

viktorklang · 2016-08-17T15:30:59Z

+1

Cheers,
√

On Aug 17, 2016 17:06, "Alexandru Nedelcu" notifications@github.com wrote:

That's fine, let me know in advance so I can prepare.

Thanks,

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
#7 (comment), or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAAqdwSBr-CVkRhkuIRLm3cg7oMughmFks5qgyNtgaJpZM4FvKcr
.

SethTisue · 2016-11-30T19:53:26Z

Closing since the SLIP process is being replaced by the new Scala Platform Process (http://www.scala-lang.org/blog/2016/11/28/spp.html). SLIP proposers are encouraged to resubmit under the new process.

dickwall added the help wanted label Aug 20, 2015

dickwall added this to the Sep 2015 SLIP mtg milestone Aug 20, 2015

dickwall modified the milestones: Aug 2015 SLIP mtg, Sep 2015 SLIP mtg Sep 7, 2015

ghost mentioned this issue Sep 17, 2015

A cats asynchronous monad (eg Task) typelevel/cats#32

Closed

dickwall modified the milestones: Oct 2015 SLIP mtg, Aug 2015 SLIP mtg Oct 11, 2015

dickwall modified the milestones: Nov 2015 SLIP mtg, Oct 2015 SLIP mtg Oct 11, 2015

jvican mentioned this issue Jul 22, 2016

Added a new SIP about possible extensions of futures and promises. scala/docs.scala-lang#295

Closed

SethTisue closed this as completed Nov 30, 2016

scala locked and limited conversation to collaborators Nov 30, 2016

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Extensions of Futures and Promises tracking #7

Extensions of Futures and Promises tracking #7

dickwall commented Aug 20, 2015

dickwall commented Sep 7, 2015

dickwall commented Sep 9, 2015

alexandru commented Sep 11, 2015

alexandru commented Sep 11, 2015

dickwall commented Sep 11, 2015

alexandru commented Sep 11, 2015

dickwall commented Oct 11, 2015

dickwall commented Nov 2, 2015

alexandru commented Jan 5, 2016

viktorklang commented Jul 13, 2016

jvican commented Jul 13, 2016 •

edited

viktorklang commented Jul 13, 2016

jvican commented Jul 22, 2016

alexandru commented Jul 22, 2016

alexandru commented Jul 22, 2016

jvican commented Jul 22, 2016

viktorklang commented Jul 23, 2016

jvican commented Jul 23, 2016

alexandru commented Aug 17, 2016

viktorklang commented Aug 17, 2016

jvican commented Aug 17, 2016

alexandru commented Aug 17, 2016

viktorklang commented Aug 17, 2016

SethTisue commented Nov 30, 2016

Extensions of Futures and Promises tracking #7

Extensions of Futures and Promises tracking #7

Comments

dickwall commented Aug 20, 2015

dickwall commented Sep 7, 2015

dickwall commented Sep 9, 2015

alexandru commented Sep 11, 2015

alexandru commented Sep 11, 2015

dickwall commented Sep 11, 2015

alexandru commented Sep 11, 2015

dickwall commented Oct 11, 2015

dickwall commented Nov 2, 2015

alexandru commented Jan 5, 2016

viktorklang commented Jul 13, 2016

jvican commented Jul 13, 2016 • edited

viktorklang commented Jul 13, 2016

jvican commented Jul 22, 2016

alexandru commented Jul 22, 2016

alexandru commented Jul 22, 2016

jvican commented Jul 22, 2016

viktorklang commented Jul 23, 2016

jvican commented Jul 23, 2016

alexandru commented Aug 17, 2016

viktorklang commented Aug 17, 2016

jvican commented Aug 17, 2016

alexandru commented Aug 17, 2016

viktorklang commented Aug 17, 2016

SethTisue commented Nov 30, 2016

jvican commented Jul 13, 2016 •

edited