Re: [elixir-core:6973] [Proposal] @dependency_of

2017-02-28 Thread Brian Cardarella
>> >> >> *José Valim* >> www.plataformatec.com.br >> Skype: jv.ptec >> Founder and Director of R >> >> On Tue, Feb 28, 2017 at 9:55 AM, Brian Cardarella <br...@dockyard.com >> > wrote: >> >>> I am doing some meta progr

Re: [elixir-core:6974] [Proposal] @dependency_of

2017-02-28 Thread Brian Cardarella
Actually, I may have solve my problem by reversing everything. :p On Tuesday, February 28, 2017 at 4:04:13 AM UTC-5, Brian Cardarella wrote: > > The problem is the compilation order. The relationship between mod A & B > is being written in __before_compile__ for each module. m

[elixir-core:6296] Re: Suggestion: Map.deep_merge

2016-09-07 Thread Brian Cardarella
This is assuming that all nested values are maps all the way down. What happens in the event of a Keyword list for example? Or a tuple? If the use-case is limiting itself to just maps of maps this works. But if the wider use-case should be supported it may make sense to consider a

[elixir-core:6258] [proposal] Kernel.fetch_in

2016-08-29 Thread Brian Cardarella
When using `with` there are several times I wish I could have reached deeper into a Map or Keyword list in a single line rather than multiple fetch statements. Ideally it would work like this: ``` map = %{foo: %{bar: "baz"}} %{:ok, "bar"} = fetch_in(map, [:foo, :bar]) :error = fetch_in(map,

Re: [elixir-core:6261] [proposal] Kernel.fetch_in

2016-08-29 Thread Brian Cardarella
allenmadsen.com > > > On Mon, Aug 29, 2016 at 8:19 AM, Allen Madsen <allen.c...@gmail.com > > wrote: > > +1 from me. Seems consistent with `get_in` and `put_in` and follows > > the semantics of `fetch`. > > Allen Madsen > > http://www.allenmadsen.com > >

Re: [elixir-core:6997] Re: Web assembly

2017-03-08 Thread Brian Cardarella
gt;> would like to chat about it, please ping me on IRC or privately by e-mail. >> >> >> >> *José Valim* >> www.plataformatec.com.br >> Skype: jv.ptec >> Founder and Director of R >> >> On Wed, Mar 8, 2017 at 5:41 PM, Brian Cardarella <

Re: [elixir-core:6998] Re: Web assembly

2017-03-08 Thread Brian Cardarella
>From what I've been reading on wasm is that pretty much everyone is waiting on the GC feature. 1.0 is more of a foot in the door release. On Wednesday, March 8, 2017 at 12:01:34 PM UTC-5, Brian Cardarella wrote: > > Confirm, for wasm 1.0. 1.1 is targeting GC > > On Wednesday

[elixir-core:7000] Understanding how guard clauses are parsed, using that AST

2017-03-09 Thread Brian Cardarella
If I quote the following: Code.string_to_quoted """ if foo do "true" else "false" end """ I get the following AST: {:if, [line: 1], [{:foo, [line: 1], nil}, [do: "true", else: "false"]]} Which makes sense to me as the last node is a list. However, `when` seems to follow

Re: [elixir-core:7002] Understanding how guard clauses are parsed, using that AST

2017-03-09 Thread Brian Cardarella
1 == 2) > {:==, [context: Elixir, import: Kernel], [1, 2]} > > In case of def, the left side (of the operator) is the call and right the > guards. > > Michał. > > On 9 Mar 2017, 12:42 +0100, Brian Cardarella <br...@dockyard.com > >, wrote: > > If I quote the follow

[elixir-core:6985] Hexdocs for ecto reference 2.1.4 in the code tags but GitHub repo doesn't have that tag

2017-03-06 Thread Brian Cardarella
Check out the code link for: https://hexdocs.pm/ecto/Ecto.Query.html#where/3 It references: https://github.com/elixir-ecto/ecto/blob/v2.1.4/lib/ecto/query.ex#L794 Which doesn't exist because the release wasn't tagged. -- You received this message because you are subscribed to the Google

[elixir-core:9580] 2020 Elixir Ecosystem Survey

2020-06-22 Thread Brian Cardarella
Hi everybody, please excuse the off-top(ish) post. The 2020 Elixir Ecosystem Survey has been released. We'd like to capture as wide an audience as possible so please take some time to complete the survey and if you can distribute it to colleagues / organizations that would be much appeciated.