Re: [Snowdrift-dev] Brainstorm for implementing multiple projects

2017-11-15 Thread Aaron Wolf
On 11/15/2017 05:24 AM, Jason Harrer wrote: > After thinking about it for awhile, I'd like to propose an alternate > recommendation for the crowdmatch step under budget calculations.  I > will start off saying that your approach will be far simpler to > implement and less resource-intensive than

Re: [Snowdrift-dev] Brainstorm for implementing multiple projects

2017-11-15 Thread Aaron Wolf
On 11/07/2017 04:34 AM, Bryan Richter wrote: > Hi all, > > Here are some initial ideas for implementing multiple projects in the > crowdmatch library. (This is not about the website.) Please take some > time to read this and provide any feedback or fresh ideas, since I > dreamed this up on my

Re: [Snowdrift-dev] Go to Definition?

2017-11-15 Thread Aaron Wolf
In general, please anyone on this thread: If you clarify suggestions that can be good for new contributors with little or no qualifications, submit merge-request changes to the TEXTEDITORS.md document. While we can't take on every issue in the Haskell ecosystem, we certainly have an interest in

Re: [Snowdrift-dev] Go to Definition?

2017-11-15 Thread Samuel Tay
> > > haskdogs sounds like it's solving a similar problem to codex. Any > insight to their relative strengths and weaknesses? > > Oh wow. I was not aware of codex, so I can't compare them, but I'll definitely be trying that out. At first glance, I think haskdogs is stack specific and codex is not,

Re: [Snowdrift-dev] Go to Definition?

2017-11-15 Thread Bryan Richter
On 11/14/2017 11:04 AM, Samuel Tay wrote: > Hasktags generates pretty much all the tags you want relevant to > your project. If you have git submodules, forks of other projects > locally, etc. then you can pass these directly via the CLI, e.g. > > hasktags -b "src deps/package1 deps/package2

Re: [Snowdrift-dev] Go to Definition?

2017-11-15 Thread Bryan Richter
On 11/14/2017 12:02 PM, David Thomas wrote: > While the general case for TH is intractable, it would probably be > pretty simple to write a script that can generate tags locations for > identifiers generated by specific, known cases - particularly > Persistent. > > At work I took a bit of a

Re: [Snowdrift-dev] Brainstorm for implementing multiple projects

2017-11-15 Thread Jason Harrer
After thinking about it for awhile, I'd like to propose an alternate recommendation for the crowdmatch step under budget calculations. I will start off saying that your approach will be far simpler to implement and less resource-intensive than mine, however I'm still proposing my recommendation