Suggestion: #d, #t and #s

[Kynde]

How about few more:

• #d to def it to something suitable for easy access ?
• #t to print it with some timing information ?
• #s to spit it to /tmp ?

[weavejester]

I think #s is a little too specific, and while #d and #t both sound useful, I'd need to think about it.

Of course you're always welcome to use hashp as a base for writing your own; I wrote hashp because Spyscope wasn't quite what I wanted.

[Kynde]

True, #s is also a little unnecessary if #d were available.

I like the no b.s. approach with this hashp. I just might investigate into adding them, but just in case some one with more free time available is anxious to add them here as PR or to another project, knowing how much I have free time at my disposal, I'd be cool with that, too.

[sparkofreason]

In a similar vein what if there were an option to send via tap>, with some known map format? Then the tap listener could do whatever, like spit to /tmp, stuff in an atom for later processing, etc. Don't think you could cover timing with that, though.

[sparkofreason]

Took a crack at generalizing this, see https://github.com/sparkofreason/hashtag. Feedback welcome and appreciated.

[sparkofreason]

Simple example of #t here: https://github.com/sparkofreason/hash-meta/blob/master/examples/clj/hasht.clj