This is a good practice, of course. But, if you hace a large code, maybe this could be dificult to read.

@akar-0 that is exactly what happened. I remember I ended using another way to calculate what you're describing.

@radhikabhat431 Yep, I did. dst is already a pointer they're passing it you as a parameter, for some reason. Otherwise, you could return any pointer you shall allocate yourself, couldn't you?

To remove the warning you may initialize i as unsigned long rather than int, or cast sizeof(strings)/sizeof(char*) to int (this way (int) sizeof(strings)/sizeof(char*)). Though it's not likely to be the cause of your code failing. Seems hard to say without more elements.

I am facing the same error! Did you find the solution?

static size can be broken

otherwise, one of the best per-the-standard solutions here

It might be better to use snake_case for the solution function definition in the Elixir's version:

defmodule SumMix do
  def sum_mix(list) do
    :your_code_here
  end
end

I think it would confuse less to new programmers (and experimented ones) due to standard coding style.

I think this is the best practice, isn't it? Is there something wrong with this?

You've inspired me, men!

Another classic one!

Thanks for taught me something new! :v

The ol' reliable baby!

I don't understand. I pass all the sample tests, but when I attempt I get:

`remove_char` should return `dst`

But I think I'm doing it:

char* remove_char(char* dst, const char* src)
{
  ...
  return dst;
}

Why is this happening? I'm training in C.

(UPDATE)

I don't know if this help, but I'm getting this on STDERR

fixture.c:13:15: warning: comparison of integers of different signs: 'int' and 'unsigned long' [-Wsign-compare]
    for(i=0; i<sizeof(strings)/sizeof(char*); i++) {
             ~^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1 warning generated.