| Title | Can't collect diverse MPS messages in order |
| Status | open |
| Priority | nice |
| Assigned user | Nick Barnes |
| Organization | Ravenbrook |
| Description | MPS clients might include code to process more than one type of MPS message, without wanting to process *all* types of message. For instance, a routine to report collections to the user might want mps_message_type_gc() and mps_message_type_gc_start(), without having to deal with mps_message_type_finalization() - which might be dealt with by a different part of the client. There is no way for such client code to obtain all such messages in order: it has to collect all of them and then sort them. |
| Analysis | mps_message_get() could allow the specification of several different message types (e.g. with a mask), and return the first matching message from the queue. That could be done with keyword args. (But maybe it would be better to wait for someone to actually encounter the problem.) |
| How found | manual_test |
| Evidence | I just know. |
| Observed in | 1.111.0 |
| Created by | Nick Barnes |
| Created on | 2013-06-13 14:17:20 |
| Last modified by | Gareth Rees |
| Last modified on | 2016-09-12 18:42:16 |
| History | 2013-06-13 NB Created. |