scala / slip

obsolete — archival use only
67 stars 15 forks source link

Extensions of Futures and Promises tracking #7

Closed dickwall closed 7 years ago

dickwall commented 9 years ago

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

https://github.com/scala/scala.github.com/pull/295

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 commented 9 years ago

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

dickwall commented 9 years ago

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 commented 9 years ago

@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 commented 9 years ago

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

Cheers,

dickwall commented 9 years ago

@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 commented 9 years ago

@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 commented 8 years ago

@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 commented 8 years ago

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

alexandru commented 8 years ago

@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 commented 8 years ago

@dickwall Is this SLIP still active?

jvican commented 8 years ago

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 commented 8 years ago

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

jvican commented 8 years ago

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 commented 8 years ago

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

alexandru commented 8 years ago

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

jvican commented 8 years ago

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! :smile:

viktorklang commented 8 years ago

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 https://github.com/scala/slip/issues/7#issuecomment-234676685, or mute the thread https://github.com/notifications/unsubscribe-auth/AAAqd09n75QXe169IzfFvsfgQq0uvOUCks5qYUrzgaJpZM4FvKcr .

jvican commented 8 years ago

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

alexandru commented 8 years ago

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 commented 8 years ago

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 https://github.com/scala/slip/issues/7#issuecomment-240434259, or mute the thread https://github.com/notifications/unsubscribe-auth/AAAqdw_a6nTdeMIxCrtpVN2IHfNBZZwVks5qgx4PgaJpZM4FvKcr .

jvican commented 8 years ago

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 commented 8 years ago

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

Thanks,

viktorklang commented 8 years ago

+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 https://github.com/scala/slip/issues/7#issuecomment-240441615, or mute the thread https://github.com/notifications/unsubscribe-auth/AAAqdwSBr-CVkRhkuIRLm3cg7oMughmFks5qgyNtgaJpZM4FvKcr .

SethTisue commented 7 years ago

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.