[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: encode-time vs decode-time
From: |
Eli Zaretskii |
Subject: |
Re: encode-time vs decode-time |
Date: |
Wed, 07 Aug 2019 17:47:18 +0300 |
> From: Stefan Monnier <address@hidden>
> Cc: Eli Zaretskii <address@hidden>, address@hidden, address@hidden,
> address@hidden
> Date: Tue, 06 Aug 2019 22:41:36 -0400
>
> Actually, while I agree that it's possible it will break something
> somewhere, it's rather unlikely.
I think our record of making such predictions is rather poor.
And anyway, suppose someone comes up with complaints about this
change: what exactly do we say in response? The reason for the change
is quite weak: it's basically an enhancement required by somewhat rare
niche use cases. How can we justify breaking someone's code on such
weak grounds?
- Re: encode-time vs decode-time, Paul Eggert, 2019/08/05
- Re: encode-time vs decode-time, Eli Zaretskii, 2019/08/06
- Re: encode-time vs decode-time, Lars Ingebrigtsen, 2019/08/07
- Re: encode-time vs decode-time, Paul Eggert, 2019/08/17
- Re: encode-time vs decode-time, Eli Zaretskii, 2019/08/17
- Re: encode-time vs decode-time, Paul Eggert, 2019/08/17
- Re: encode-time vs decode-time, Lars Ingebrigtsen, 2019/08/17
- Re: encode-time vs decode-time, Paul Eggert, 2019/08/17
- Re: encode-time vs decode-time, Stefan Monnier, 2019/08/17
- Re: encode-time vs decode-time, Paul Eggert, 2019/08/17