Re: [dylan] Stream locking (was: Method combinations as a design pattern for locking)
Hannes Mehnert <[email protected]> Wed, 18 Dec 2013 16:51:40 +0100
| Newsgroups | gmane.comp.lang.dylan.gwydion.devel |
|---|---|
| Message-ID | <[email protected]> |
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA384 On 12/18/2013 13:24, Hannes Mehnert wrote: > I also do not understand why you want to remove (in your branch) > both the init-value for the private-stream-lock-value slot of > <basic-stream>, as well as the calls to with-stream-locked from > within io? Does the test whether stream-lock is non-false (in > lock-stream) lower the performance in a significant way? I actually understand a bit better now... The lock-stream is an open generic, thus with-stream-locked turns into two GF dispatches all the time (one for lock, the other for unlock-stream). Hannes -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (FreeBSD) iQIcBAEBCQAGBQJSscSMAAoJELyJZYjffCjuYt0QAKndNvuTXp06Nm4VHRpgvQmo GvJCVWVnFaWChmXLL2m7KA8YwyqKpOV36m/D5nXsjXG0NBsf8P7gbJ/dABU4BZSo OR/aMxINgeVsEUtuCfBr0eeRBfWLnDGEw+QaScv2nmj3Sg9BY04TCPyB1lxIB79/ paFh8UxgY5PLiiY05jjW2fY0IkGEtN0/psZBNx8TveppQG9RKC9JxgBWvMWdMAvd 9yGOVnN5dvyXx1W9Nkh1VL3PHg+d/tGgRcKjoN4l50IPVUEOgSf/q/KX3kMHf7KU BTCd8MlANcr0xU+wochfo651CpVjZtSJjvKB96SkTkAMQ5azAwu4ZNK2pgCzb3ow w7RcCNWrYEw74g3SH9SrdhQglZNyYJZ18jcumWZ0rOwIJ0nZCIfuGX/5kdlAOwB8 sp9gAeKtlEFaIjPnYXBujMwfhSE4BMdrHaV6+fbdqWcNwcP+yJsxTVE9mPbTn4wx /AEhSoCTq4pngMjTDX9ThrPnVHl24v5JolMxGAvknFugG6quhsOvy3bnu/u4lkKR flXWjkYaXUPJhrnST9PFXwcVXwcvA/SjfnChzxpEUpHgq7zB6aeN/KD46JuywN7N b/0y4684ol+SwSg8e4kXgEqJh9+o5M0B1FyvksQOLtxerWNAnuHeaEYPAqmkpcFV 4/ScawpVCzMyOi2/+n5e =i4wj -----END PGP SIGNATURE----- _______________________________________________ hackers mailing list [email protected] https://lists.opendylan.org/mailman/listinfo/hackers