From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Christopher Allan Webber Newsgroups: gmane.lisp.guile.devel Subject: Re: wip-ports-refactor Date: Wed, 13 Apr 2016 09:27:55 -0500 Message-ID: <87fuupbn2s.fsf@dustycloud.org> References: <87twjempnf.fsf@pobox.com> <87pou282vo.fsf@dustycloud.org> <87potvmco3.fsf@pobox.com> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Trace: ger.gmane.org 1460557696 19712 80.91.229.3 (13 Apr 2016 14:28:16 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Wed, 13 Apr 2016 14:28:16 +0000 (UTC) Cc: guile-devel@gnu.org To: Andy Wingo Original-X-From: guile-devel-bounces+guile-devel=m.gmane.org@gnu.org Wed Apr 13 16:28:10 2016 Return-path: Envelope-to: guile-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1aqLm5-00082o-L4 for guile-devel@m.gmane.org; Wed, 13 Apr 2016 16:28:09 +0200 Original-Received: from localhost ([::1]:44848 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aqLm4-0001gx-W8 for guile-devel@m.gmane.org; Wed, 13 Apr 2016 10:28:08 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:39487) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aqLlw-0001Xv-BI for guile-devel@gnu.org; Wed, 13 Apr 2016 10:28:06 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1aqLlt-0007J4-3g for guile-devel@gnu.org; Wed, 13 Apr 2016 10:28:00 -0400 Original-Received: from dustycloud.org ([50.116.34.160]:32864) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aqLls-0007Is-W4 for guile-devel@gnu.org; Wed, 13 Apr 2016 10:27:57 -0400 Original-Received: from oolong (localhost [127.0.0.1]) by dustycloud.org (Postfix) with ESMTPS id 2ECE826707; Wed, 13 Apr 2016 10:27:56 -0400 (EDT) User-agent: mu4e 0.9.13; emacs 24.5.1 In-reply-to: <87potvmco3.fsf@pobox.com> X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 50.116.34.160 X-BeenThere: guile-devel@gnu.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: "Developers list for Guile, the GNU extensibility library" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guile-devel-bounces+guile-devel=m.gmane.org@gnu.org Original-Sender: "guile-devel" Xref: news.gmane.org gmane.lisp.guile.devel:18282 Archived-At: Andy Wingo writes: > Hi! > > Summarizing my reply over IRC: > > On Thu 07 Apr 2016 06:16, Christopher Allan Webber writes: > >> So, does this branch replace ethreads, or compliment it? Where should= I >> be focusing my (currently limited) review / integration attempt energy= ? >> I've been hoping to review ethreads this week but now I'm unsure. Can >> you explain how the efforts currently relate? > > This branch hopes to make the "eports" part of that branch unnecessary. > However actually implementing user-space threads =C3=A0 la ethreads is = out of > scope, as is the epoll wrapper. > >> One other question is if this will help in the "no nice way to do cust= om >> binary ports" stuff that was blocking the >> tls-enabled-ports-in-guile-proper thing... > > Was that the blocker? Ludovic explains here: https://lists.gnu.org/archive/html/guile-devel/2015-09/msg00042.html > Anyway the current branch's ports are verrrrrrrry close to R6RS binary > ports, so this shouldn't be a difficulty any more. I haven't > implemented custom binary I/O ports (we have input-only and > output-only but not both) yet, but it should be doable. Yay! It does sound like that might fix it. (Admittedly it's a bit beyond me.) >> As I've said, I'm not tied to 8sync specifically if doing something mo= re >> internally makes more sense. (Even if I have a nice site and logo >> coming together now ;)) > > I think keep rolling with 8sync :) It has a nice brand, it's filling a > need that probably won't be filled in 2.2.0, it's laying groundwork for > future Guile features. Yay! Ok, I will do so. > Eventually I would like user-space threads in Guile proper, > implemented in terms of delimited continuations, and that implies a > scheduler too. But that's a bit far off. My goal is to make it > possible to add such a thing during the 2.2.x series, probably first > as a library (8sync) and eventually as a core Guile feature. > > Andy Sounds good. But here's a question: we haven't accepted many contributions yet to 8sync. Would it make sense now to require copyright assignment for the project? (We don't, yet.) That might slow development a bit but could make future merging into Guile, if such a thing were to be done, easier. - Chris