> You have to pitch people on the potential benefits of downloading your
> library *before* they click the download link for it, or they mostly
> never will.
Sold. I've learned my lesson.
--
You received this message because you are subscribed to the Google
Groups "Clojure" group.
To post to th
On Mon, Jan 9, 2012 at 3:43 PM, Jay Fields wrote:
> On Mon, Jan 9, 2012 at 3:20 PM, Cedric Greevey wrote:
>
>> Talk about completely missing the point.
>
> I had no idea what core.unify would be used for either. However, the
> email included a link to the github page, and the Readme on the github
On Mon, Jan 9, 2012 at 3:20 PM, Cedric Greevey wrote:
> Talk about completely missing the point.
I had no idea what core.unify would be used for either. However, the
email included a link to the github page, and the Readme on the github
page included a link called "more information" and several
On Mon, Jan 9, 2012 at 2:16 PM, Michael Fogus wrote:
>> Not really, not with a single fairly generic word like "unification".
>
> In the amount of time that you spent lecturing me on good library
> release note practices you could have learned what unification was,
> read the code, and decided if
> unify, but I have no idea where to begin! Having short description and some
> simple use cases in announce would be great.
I do not disagree. Those elements will be in place by the 1.0.0
release (as listed in the "planned" section). In the meantime,
patches welcomed.
--
You received this mess
On Mon, Jan 9, 2012 at 2:08 PM, Sean Corfield wrote:
> On Mon, Jan 9, 2012 at 11:00 AM, Cedric Greevey wrote:
>> On Mon, Jan 9, 2012 at 1:45 PM, Michael Fogus wrote:
>>> Google also helps too. :-)
>> Not really, not with a single fairly generic word like "unification".
>
> #1 result: wikipedia,
First of all, thank you for your work!
But actually I agree with Cedric. He definitely has a point. I'd love to
try unify, but I have no idea where to begin! Having short description and
some simple use cases in announce would be great.
Please do not take this as a critisism, but rather as a w
> Not really, not with a single fairly generic word like "unification".
In the amount of time that you spent lecturing me on good library
release note practices you could have learned what unification was,
read the code, and decided if it filled any of your needs.
Hint. My library has very littl
On Mon, Jan 9, 2012 at 11:00 AM, Cedric Greevey wrote:
> On Mon, Jan 9, 2012 at 1:45 PM, Michael Fogus wrote:
>> Google also helps too. :-)
> Not really, not with a single fairly generic word like "unification".
#1 result: wikipedia, which has a disambiguation page with the second entry:
"Unifi
On Mon, Jan 9, 2012 at 1:45 PM, Michael Fogus wrote:
>> Yes, but what exactly are these "unification binding, subst, and
>> unification functions"?
>
> This is information that seems a bit odd to include in a set of
> release notes, but I suppose a link to where such information could be
> found i
> Yes, but what exactly are these "unification binding, subst, and
> unification functions"?
This is information that seems a bit odd to include in a set of
release notes, but I suppose a link to where such information could be
found is warranted.
> In other words, I'm a developer. I have some co
On Mon, Jan 9, 2012 at 8:00 AM, Fogus wrote:
> core.unify v0.5.2 Release Notes
> ===
>
> core.unify is a Clojure contrib library providing the following
> features:
>
> * Factory functions for constructing unification binding, subst, and
> unification functions, with or
core.unify v0.5.2 Release Notes
===
core.unify is a Clojure contrib library providing the following
features:
* Factory functions for constructing unification binding, subst, and
unification functions, with or without occurs checking
* Packaged functions for unificati
13 matches
Mail list logo
