Re: [elixir-core:11296] Multi-letter (uppercase) sigils

2023-03-04 Thread Amos King - Binary Noggin
, it makes sense, but does it for something like Date? Changing the interpolation syntax saves a small class of errors in specific circumstances but creates multiple ways to interpolate that lead to confusion, IMO. Cheers, Amos King, CEO <https://twitter.com/binarynoggin>

Re: [elixir-core:10610] Introduce :let in for-comprehensions

2021-12-16 Thread Amos King - Binary Noggin
&1]) > end > > Amos King, CEO <https://twitter.com/binarynoggin> <https://www.facebook.com/BinaryNoggin/> <https://www.instagram.com/binarynoggin/> <https://www.linkedin.com/company/binary-noggin> 573-263-2278 a...@binarynoggin.com On Thu, Dec 16, 2021 at

Re: [elixir-core:10158] Ranges with steps

2021-03-22 Thread Amos King - Binary Noggin
Yes, the `1..9//2` communicates intention a little better than `a..b..c` IMO. Amos King, CEO <https://twitter.com/binarynoggin> <https://www.facebook.com/BinaryNoggin/> <https://www.instagram.com/binarynoggin/> <https://www.linkedin.com/company/binary-

Re: [elixir-core:10153] Ranges with steps

2021-03-22 Thread Amos King - Binary Noggin
` but that comes with other implementation issues. I like the proposals using a different operator for the step. `a..b\\c`? Amos King, CEO <https://twitter.com/binarynoggin> <https://www.facebook.com/BinaryNoggin/> <https://www.instagram.com/binarynoggin/> <https://www.linkedin.com/compan

Re: [elixir-core:10144] Ranges with steps

2021-03-22 Thread Amos King
What about something closer to Haskell’s ranges? [first, second..last] is their syntax and the step in inferred by the difference between first and second. 1..2..n would step by one. 1..3..n is step by two. 1..2..0 would be empty, etc. Negative steps. 1..0..-10. 1..0..10 would return an empty

Re: [elixir-core:10116] [Proposal] range pattern matching in case without when

2021-03-13 Thread Amos King
to reduce the ambiguity. Amos King CEO Binary Noggin > On Mar 13, 2021, at 06:26, Igor Silva wrote: > > Current behavior > > case ?a do > x when x in ?a..?z -> # code > x when x in ?A..?Z -> # code > _ -> # code > end > > Desired behavior >

Re: [elixir-core:9362] [Proposal] Add Function.const/2

2020-02-05 Thread Amos King
I’m voting for adding the concept. Bruce sold me with his arguments. Amos King CEO Binary Noggin > On Feb 5, 2020, at 15:16, Jesse Claven wrote: > >  > Thanks everyone for the good discussion! Especially Bruce who was better able > to explain what I was trying to explain. I

Re: [elixir-core:9357] [Proposal] Add Function.const/2

2020-02-04 Thread Amos King
ested many >>> times previously, was that at some point everyone agreed that it would >>> improve Elixir's documentation, because it is easier to search for than >>> `&(&1)`. >>> >>> The `const` pattern is much less wide-spread. In e.g. Haskell it s

Re: [elixir-core:9341] [Proposal] Add Function.const/2

2020-01-29 Thread Amos King - Binary Noggin
n't know how useful that would be in the long run. I know it is common in function programming, but I don't see it being extremely helpful in Elixir. I'm ready to be convinced. Cheers, Amos King CEO Binary Noggin http://binarynoggin.com #business https://elixiroutlaws.com #elixir podcast h

Re: [elixir-core:8887] Re: [Proposal] identity function

2019-07-02 Thread Amos King
This is a basic of functional programming and has my vote. Amos King CEO Binary Noggin > On Jul 2, 2019, at 10:26, Chris Keathley wrote: > > I'm also in favor of including an `id` function. > >> On Tue, Jul 2, 2019 at 8:52 AM Bruce Tate wrote: >> Strong +1 from me.

Re: [elixir-core:8467] [Proposal] Add invert() method to Map module

2019-02-06 Thread Amos King - Binary Noggin
take advantage of it. Amos King CEO Binary Noggin http://binarynoggin.com #business https://elixiroutlaws.com #elixir podcast http://thisagilelife.com #podcast === I welcome VSRE emails. Learn more at http://vsre.info

Re: [elixir-core:8437] [Proposal] Shorthand to filter tests by multiple line numbers

2019-01-09 Thread Amos King
of applications. I’d rather save the time there and not have to chain command line calls. Chaining command line calls also has the added issue of one command has a failure and the rest don’t run. Amos King Binary Noggin > On Jan 9, 2019, at 04:46, Sven Gehring wrote: > > I'd personally prefer t

Re: [elixir-core:7638] [proposal]

2017-11-30 Thread Amos King
Thank you for the feedback. I will look into doing just that. Amos Amos King Owner Binary Noggin http://binarynoggin.com #business http://thisagilelife.com #podcast === I welcome VSRE emails. Learn more at http://vsre.info

[elixir-core:7635] [proposal]

2017-11-30 Thread Amos King
the module, but since the code is already in the core I don't think another hex package is the right solution. I'm willing to do this, but I want to see what others think before I put the work into it. Would anyone else find this useful? Amos King Owner Binary Noggin http://binarynoggin.com #business

Re: [elixir-core:7080] Re: Proposal: Enum.take/1

2017-04-25 Thread Amos King
core must be maintained in the core. In thinking through this like the explicitness of the name, but it doesn't buy much more than utilizing `Enum.take\2`. Amos King Owner Binary Noggin http://binarynoggin.com #business http://thisagilelife.com #podcast ===

Re: [elixir-core:7074] Re: Proposal: Enum.take/1

2017-04-22 Thread Amos King
You want to add a default of 1 to Enum.take/2? I personally don't mind that but I think it takes away from the explicit nature of the module. I prefer explicitness if we are only saving a few keystrokes. Amos King Binary Noggin > On Apr 22, 2017, at 04:12, Sam Davies <sampdav...@gma

Re: [elixir-core:6887] Re: Sorting maps when inspecting

2017-02-15 Thread Amos King
Before jumping on this should we be asking why the decision was made to not sort if there are more than 32 keys? Maybe there is a performance concern, and if we want sorted keys we should be sending a different message? Amos King Owner Binary Noggin http://binarynoggin.com #business http

Re: [elixir-core:6820] Re: Proposal: Behaviours, defoverridable and impl

2017-01-19 Thread Amos King
not a fan of the true. I understand that it appears directly above the header in question, but I like the explicit version. Would this only go over one clause?, or would it have to be over top of each clause? Cheers, Amos Amos King Owner Binary Noggin http://binarynoggin.com #business http://thisagi

Re: [elixir-core:6770] improve OptionParser?

2016-12-22 Thread Amos King
What is the use case? Amos King Binary Noggin > On Dec 22, 2016, at 20:11, Chris Keele <d...@chriskeele.com> wrote: > > Currently only single-letter aliases are allowed. Is this intentional or > would the capacity to alias, for instance, option "foo"

Re: [elixir-core:6699] I think the new 1.4 warning about missing () on zero arity functions is a cure that's worse than the disease

2016-12-05 Thread Amos King
Is this something that could be solved with an external tool added to your build chain? Amos King Binary Noggin > On Dec 5, 2016, at 09:29, Allen Madsen <allen.c.mad...@gmail.com> wrote: > > I would also argue for case 3. > >> However, it does not solve the contextual

Re: [elixir-core:6673] I think the new 1.4 warning about missing () on zero arity functions is a cure that's worse than the disease

2016-12-03 Thread Amos King
Actually could this be solved externally to the language with a static code analysis tool? Amos King Binary Noggin > On Dec 3, 2016, at 08:34, Allen Madsen <allen.c.mad...@gmail.com> wrote: > > It looks like this was already discussed here: > https://github.com/elixir-lang/

Re: [elixir-core:6672] I think the new 1.4 warning about missing () on zero arity functions is a cure that's worse than the disease

2016-12-03 Thread Amos King
. I'm In favor of the one caveat of the anonymous functions needing to have the parentheses and a dot in favor of being able to use bare words. Amos King Binary Noggin > On Dec 3, 2016, at 08:34, Allen Madsen <allen.c.mad...@gmail.com> wrote: > > It looks like this was already

Re: [elixir-core:6670] I think the new 1.4 warning about missing () on zero arity functions is a cure that's worse than the disease

2016-12-03 Thread Amos King
In my experience the minimize scope of data binding keeps it pretty straightforward. Amos King Binary Noggin > On Dec 3, 2016, at 07:50, Michał Muskała <mic...@muskala.eu> wrote: > > The ambiguity, that bit me already several times is in the code that looks > like this: &

Re: [elixir-core:6668] I think the new 1.4 warning about missing () on zero arity functions is a cure that's worse than the disease

2016-12-03 Thread Amos King
I prefer being able to use the bare words. It makes refactoring simpler to move between a variable and a method which I do regularly. The warning seems strange since there isn't an ambiguity that is being decided. I'm on board with Dave here. Amos King Binary Noggin > On Dec 3, 2016, at

Re: [elixir-core:6663] Adding __APP__ or something similar

2016-12-02 Thread Amos King
I think I like the App.defmodule more than the other solutions. It is more focused on the area of concern and doesn't need to be a new part of Elixir. Amos King Owner Binary Noggin http://binarynoggin.com #business http://thisagilelife.com #podcast

Re: [elixir-core:6642] Adding __APP__ or something similar

2016-11-30 Thread Amos King
Here here. Amos King Binary Noggin > On Nov 30, 2016, at 16:47, Michael Terry <mich...@michaelterry.org> wrote: > > > All the time. Naming things in programming is hard and I never get it right > at first. Knowing that it may be a relative pain to rename a proje