Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
Request about unhash / unfunction / unset
- X-seq: zsh-workers 34765
- From: Larry Schrof <larrys@xxxxxx>
- To: "zsh-workers@xxxxxxx" <zsh-workers@xxxxxxx>
- Subject: Request about unhash / unfunction / unset
- Date: Mon, 23 Mar 2015 21:06:26 +0000
- Accept-language: en-US
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/simple; d=fb.com; h=from : to : subject : date : message-id : content-type : mime-version; s=facebook; bh=ArXyT8yezlHyYiCZ9/WQi/oPxf+ghhgRFZh+TbNVyR4=; b=ktpg4mi9oj3QYPWuyrtmCnwoR2viBgDZtp7Ageuv1wGkJRbjPJ4hJVQJpQts7hvJ4/vg xEkknrJf1GqhPj4JVT9zB1M6hCkpH+hvK9xUi6FkY9GXY4AtsYYAThkUg1qaY0ZGE3L1 MgYAHm7leeKJ6SX+wtWYMU3AXK2PRo1WnsY=
- List-help: <mailto:zsh-workers-help@zsh.org>
- List-id: Zsh Workers List <zsh-workers.zsh.org>
- List-post: <mailto:zsh-workers@zsh.org>
- Mailing-list: contact zsh-workers-help@xxxxxxx; run by ezmlm
- Thread-index: AdBlrNKbtHSp36/FRna+dNq1d8jBkA==
- Thread-topic: Request about unhash / unfunction / unset
I would like to humbly request that if zsh is asked to unhash an entry that is not in the hash table, it silently does nothing if the entry was not previously there. (Instead of generating an error message.)
I think in the vast majority of use cases, the user just wants to ensure an element is not in the hash table. I don't think they care if it was or wasn't in the table before the call to unhash. And the operation is idempotent, so there's even less motivation to warn based on the initial state.
Same request for unfunction and unalias.
Thanks for your consideration!
Messages sorted by:
Reverse Date,
Date,
Thread,
Author