Re: [core libraries] Re: Add taggedTrace to Debug.Trace

> But there are > plenty of little things in there which mean I would still use my own > library, not Debug.Trace, even if it did have a few extra functions. Oh, I see. That's actually possible. Okay, I'll withdraw my suggestion this time. Thanks! 2018年6月12日(火) 14:25 Evan Laforge : > I agree

Re: [core libraries] Re: Add taggedTrace to Debug.Trace

I agree that tags are necessary, and in fact I recently ported my internal debug library to cabal because now that I'm doing more stuff with cabal I find life too difficult without my accustomed debug library. For reference, it is this, but nothing fancy:

Re: [core libraries] Re: Add taggedTrace to Debug.Trace

Can anyone give me more feedback? I'm interested especially in my last reply. 2018年6月8日(金) 9:19 Yuji Yamamoto : > Almost any formatting will do. At least I never care. > I assume those APIs would be used for very ad-hoc use (like the other APIs > in Debug.Trace). > And debug codes put by such

Re: [core libraries] Re: Add taggedTrace to Debug.Trace

Almost any formatting will do. At least I never care. I assume those APIs would be used for very ad-hoc use (like the other APIs in Debug.Trace). And debug codes put by such cases are deleted or disabled by NoTrace package in production. I want handy

Re: [core libraries] Re: Add taggedTrace to Debug.Trace

Edward Kmett writes: > What different users would do with such a prefix, how to display it, > etc. varies just enough that i’m somewhat hesitant to grow the API. > I’m a very weak -1. But I’d happily let anybody else on the committee > override that if they had a strong preference. > Right, as I

Re: [core libraries] Re: Add taggedTrace to Debug.Trace

What different users would do with such a prefix, how to display it, etc. varies just enough that i’m somewhat hesitant to grow the API. I’m a very weak -1. But I’d happily let anybody else on the committee override that if they had a strong preference. -Edward > On Jun 7, 2018, at 5:40 PM,