nrook posted:

also, basic list operations appear to be a pain in the rear end in java, or at least they were before java 8. can't use java 8 at work yet so I don't have opinions about it, but it probably fixes some of this

like, I had an object foo in a list today, and I wanted to take all the objects such that foo.bar == "hi", and get their indices in the list

you know, like

code:

[i for i, j in enumerate(the_list) if j.bar == "hi"]

or

code:

IEnumerable<int> IndicesWhereBarIsHi(IList<Foo> foos) {
  for (int i in Enumerable.Range(0, foos.Count) {
    if (foos[i].bar == "hi") {
      yield return i;
    }
  }
}

which is better than it looks, because I included the function declaration. unless you're doing it mid-logic, then it is just what it looks like cuz you gotta declare a closure. you can and should probably define your own IEnumerable<T>.Enumerate extension method like the python one above though, which makes this cleaner, and lets you use fake sql syntax if you're an idiot

how do you do that in java? you do

code:

List<Integer> indices = new ArrayList<Integer>()
for (old-style for loop like a caveman) {
  if (Foos.get(i).bar == "hi") {
    indices.append(i);
  }
}

which sucks! especially since it tempts people to add logic into the for loop, and has mutable state and stuff like that

coffeetable posted:

as to scala, i haven't used it but i know many of its headline features are now in java 8, so you might wanna try that first.

nrook posted:

nrook posted:

also, basic list operations appear to be a pain in the rear end in java, or at least they were before java 8. can't use java 8 at work yet so I don't have opinions about it, but it probably fixes some of this

like, I had an object foo in a list today, and I wanted to take all the objects such that foo.bar == "hi", and get their indices in the list

you know, like

code:

[i for i, j in enumerate(the_list) if j.bar == "hi"]

or

code:

IEnumerable<int> IndicesWhereBarIsHi(IList<Foo> foos) {
  for (int i in Enumerable.Range(0, foos.Count) {
    if (foos[i].bar == "hi") {
      yield return i;
    }
  }
}

which is better than it looks, because I included the function declaration. unless you're doing it mid-logic, then it is just what it looks like cuz you gotta declare a closure. you can and should probably define your own IEnumerable<T>.Enumerate extension method like the python one above though, which makes this cleaner, and lets you use fake sql syntax if you're an idiot

how do you do that in java? you do

code:

List<Integer> indices = new ArrayList<Integer>()
for (old-style for loop like a caveman) {
  if (Foos.get(i).bar == "hi") {
    indices.append(i);
  }
}

which sucks! especially since it tempts people to add logic into the for loop, and has mutable state and stuff like that

prefect posted:

code:

grep { $_->bar == 'hi' } @array;

(i can't help it; i still miss perl sometimes)

Shinku ABOOKEN posted:

i am doing c# so no can do

e:

lmaaaaaaaaaaaaaao look at this
http://visualstudiogallery.msdn.microsoft.com/9ba50f8d-f30c-4e33-ab19-bfd9f56eb817/showImage/86649

~Coxy posted:

guy at my work uses comic sans 14 pt bold as his ide typeface

nrook posted:

also, basic list operations appear to be a pain in the rear end in java, or at least they were before java 8. can't use java 8 at work yet so I don't have opinions about it, but it probably fixes some of this

like, I had an object foo in a list today, and I wanted to take all the objects such that foo.bar == "hi", and get their indices in the list

you know, like

code:

[i for i, j in enumerate(the_list) if j.bar == "hi"]

or

code:

IEnumerable<int> IndicesWhereBarIsHi(IList<Foo> foos) {
  for (int i in Enumerable.Range(0, foos.Count) {
    if (foos[i].bar == "hi") {
      yield return i;
    }
  }
}

which is better than it looks, because I included the function declaration. unless you're doing it mid-logic, then it is just what it looks like cuz you gotta declare a closure. you can and should probably define your own IEnumerable<T>.Enumerate extension method like the python one above though, which makes this cleaner, and lets you use fake sql syntax if you're an idiot

how do you do that in java? you do

code:

List<Integer> indices = new ArrayList<Integer>()
for (old-style for loop like a caveman) {
  if (Foos.get(i).bar == "hi") {
    indices.append(i);
  }
}

which sucks! especially since it tempts people to add logic into the for loop, and has mutable state and stuff like that

Shaggar posted:

yes. but he thinks putting retarded garbage you will never reuse into reusable functions is a thing that people should do

Symbolic Butt posted:

idk about that because I don't even know what are java's std functions, I was just thinking in a general case

Dessert Rose posted:

the java code is correct afaik but the c# code is functionally equivalent to

code:

foos.Where(f => f == "hi")

Dessert Rose posted:

the java code is correct afaik but the c# code is functionally equivalent to

code:

foos.Where(f => f == "hi")

Dessert Rose posted:

code:

foos.Where(f => f == "hi")

Shaggar posted:

actually hes trying to get the indexes of the foos where their bar value is "hi" instead of selecting the foos (which is stupid). the linq would be something like

C# code:

var hibarIndexes = foos.Select((foo,index) => new {foo,index}).Where(x=>x.foo.bar=="hi").Select(x=>x.index);

Bloody posted:

im the code in a high level language where indices in a list are being janitored

Bloody posted:

ctps: making monstrous nested struct/union beasts

like, a union of a struct and an array and the struct is full of unions of bits and bytes and also loose bytes and aughughguh its like russian nesting dolls made of poo poo

coffeetable posted:

why

Morkai posted:

my chickens, they have come home to roost. currently tasked with "performance optimization" of our EF use. lol

Morkai posted:

my chickens, they have come home to roost. currently tasked with "performance optimization" of our EF use. lol

Valeyard posted:

doing software engineering at my university is literally just CS except you get less choice of classes in your final year, and in the third year there is a mandatory summer work placement with accompanying essay/presentation

apt gangbang posted:

you're lying

Valeyard posted:

mobile software engineering is the only one that is different, becaause you get to drop the database class and take an embedded systems class in its place

Uncomfortable Gaze posted:

what? that's dumb, database design is really important in mobile. embedded systems class is cool though, they should be required to take both