|
Thread Rules 1. This is not a "do my homework for me" thread. If you have specific questions, ask, but don't post an assignment or homework problem and expect an exact solution. 2. No recruiting for your cockamamie projects (you won't replace facebook with 3 dudes you found on the internet and $20) 3. If you can't articulate why a language is bad, don't start slinging shit about it. Just remember that nothing is worse than making CSS IE6 compatible. 4. Use [code] tags to format code blocks. |
Okay I've got a question for the professionals out there
on my resume, what sort of terminology should I use to explain how familiar I am with languages/systems?
For example, I've been programming almost exclusively in Java, have finished 2 rigorous classes on it, and feel like with just a small amount of research I could do most of what there is to do in Java. But there's still lots to learn, of course. Would it be reasonable to say that I am "fluent in java" on my resume?
Let's say I finish a large introductory text on python and learn all the concepts, and I am now capable of writing basic python programs. could I say that I am "familiar" with python?
etc etc
thanks 
also, I am filling out an online application for an internship and they ask me "are you familiar with high and low level languages". I feel like the answer is obviously "no" since I don't know any low level languages. I do, however, have a basic idea of how assembly works.. But they are wanting me to actually know how to program in assembly / something comparable?
|
When I'm looking at intern or new hire resumes I look for projects that the person has worked on. Most of the new grads have a senior design project that I'll ask them questions about during the interview and ideally some other work that they were interested in. Having some giant list of languages and frameworks you've seen or worked on is fairly useless in my opinion, but different people look for different things.
|
On January 07 2017 02:44 spinesheath wrote:First of all you should sort your lines by length. There should be a sort-method readily available in Java, you might have to pass it a Comparer of sorts, which converts a line into its length. The result of this step is a sorted list of lines. Then in the second step, you iterate over the sorted lines. For each line, you check it against all lines, which you do again by iterating over the sorted lines, skipping the one you're currently checking. If you find one that doesn't intersect any line, you return that one as a result. It is the smallest one because it's the first in the sorted list. There is no recursion here. It's a naive approach, but clean and simple. It's O(n^2). More sophisticated approaches probably would keep the first part, but tweak the second part to use sort of a divide and conquer approach, but that won't be very simple at all. I can imagine O(n log n), but I don't know if it actually is possible. This approach includes a number of pointless checks, in the worst case 50%. This is because I check against all lines without skipping the pairs already covered. We can avoid that easily by storing the sorted lines in a list, then iterate over the list by index. If we are currently at list[5], we only check against list[6] and beyond: for(int i = 0; i < list.Count; ++i) { for(int k = i + 1; k < list.Count; ++k) { check if list[i] intersects list[k]; } }
Still is O(n^2) though. Always ask yourself if you can split your problem into smaller chunks. Sort first, check after. Simple approach first, optimization after. Also Java or rather the JVM is not well equipped for heavy recursion. Don't avoid recursion at all costs, but if you're doing a lot of work with deep recursion, you probably should try to avoid it. Why keep a list? You know you've checked intersections with all the lines up to i-1, so just check i+1 forward. This has to go together with roomofmush's optimization of removing intersecting lines from the list, of course. That seems like a pretty efficient way of doing it. Not quite sure how you could optimize further (which is of course Nesserev's cue to show how to make a vast improvement ).
|
That's what the list is for, so I can do index access. And in the inner for, notice the initialization of k.
|
On January 07 2017 06:25 travis wrote:Okay I've got a question for the professionals out there on my resume, what sort of terminology should I use to explain how familiar I am with languages/systems? For example, I've been programming almost exclusively in Java, have finished 2 rigorous classes on it, and feel like with just a small amount of research I could do most of what there is to do in Java. But there's still lots to learn, of course. Would it be reasonable to say that I am "fluent in java" on my resume? Let's say I finish a large introductory text on python and learn all the concepts, and I am now capable of writing basic python programs. could I say that I am "familiar" with python? etc etc thanks  also, I am filling out an online application for an internship and they ask me "are you familiar with high and low level languages". I feel like the answer is obviously "no" since I don't know any low level languages. I do, however, have a basic idea of how assembly works.. But they are wanting me to actually know how to program in assembly / something comparable? You might rate yourself on your skills on a scale of 1 to either 3, 5 or 10. Also, nobody wants you to know how to program in assembly. I know how to do it and never had to use it for anything professionally. I don't rate my skills in my resume. They are just a comma separated list. I don't even think that people take this stuff seriously.
What matters most is always projects. If you feel like with just a small amount of research I could do most of what there is to do in Java, do something with it. Not just say you're "fluent in java" or whatever the bull crap that is. You're going to be a fresh grad. Projects will be a yes/no question for you, not a "wh-" question (unlike more senior developers). If you have something to show, you're golden.
Also, Low level languages are C and C++. I don't even think your recruiter/boss/manager can program in assembly, even if s/he is a "lead/staff/senior embedded systems developer". They only teach assembly to students so that they have a better idea about what happens under the hood.
|
On January 07 2017 23:09 Djagulingu wrote:Show nested quote +On January 07 2017 06:25 travis wrote:Okay I've got a question for the professionals out there on my resume, what sort of terminology should I use to explain how familiar I am with languages/systems? For example, I've been programming almost exclusively in Java, have finished 2 rigorous classes on it, and feel like with just a small amount of research I could do most of what there is to do in Java. But there's still lots to learn, of course. Would it be reasonable to say that I am "fluent in java" on my resume? Let's say I finish a large introductory text on python and learn all the concepts, and I am now capable of writing basic python programs. could I say that I am "familiar" with python? etc etc thanks  also, I am filling out an online application for an internship and they ask me "are you familiar with high and low level languages". I feel like the answer is obviously "no" since I don't know any low level languages. I do, however, have a basic idea of how assembly works.. But they are wanting me to actually know how to program in assembly / something comparable? You might rate yourself on your skills on a scale of 1 to either 3, 5 or 10. Also, nobody wants you to know how to program in assembly. I know how to do it and never had to use it for anything professionally. I don't rate my skills in my resume. They are just a comma separated list. I don't even think that people take this stuff seriously. What matters most is always projects. If you feel like with just a small amount of research I could do most of what there is to do in Java, do something with it. Not just say you're "fluent in java" or whatever the bull crap that is. You're going to be a fresh grad. Projects will be a yes/no question for you, not a "wh-" question (unlike more senior developers). If you have something to show, you're golden. Also, Low level languages are C and C++. I don't even think your recruiter/boss/manager can program in assembly, even if s/he is a "lead/staff/senior embedded systems developer". They only teach assembly to students so that they have a better idea about what happens under the hood. There are a few select positions where you need to use assembly though. Highly unlikely travis will end up with one of these but perfectly possible. I wouldnt recommend learning it though unless out of curiousity. If you really need it for your job it will probably be something very specific which you will need to learn again anyways.
|
On January 08 2017 00:52 RoomOfMush wrote:Show nested quote +On January 07 2017 23:09 Djagulingu wrote:On January 07 2017 06:25 travis wrote:Okay I've got a question for the professionals out there on my resume, what sort of terminology should I use to explain how familiar I am with languages/systems? For example, I've been programming almost exclusively in Java, have finished 2 rigorous classes on it, and feel like with just a small amount of research I could do most of what there is to do in Java. But there's still lots to learn, of course. Would it be reasonable to say that I am "fluent in java" on my resume? Let's say I finish a large introductory text on python and learn all the concepts, and I am now capable of writing basic python programs. could I say that I am "familiar" with python? etc etc thanks  also, I am filling out an online application for an internship and they ask me "are you familiar with high and low level languages". I feel like the answer is obviously "no" since I don't know any low level languages. I do, however, have a basic idea of how assembly works.. But they are wanting me to actually know how to program in assembly / something comparable? You might rate yourself on your skills on a scale of 1 to either 3, 5 or 10. Also, nobody wants you to know how to program in assembly. I know how to do it and never had to use it for anything professionally. I don't rate my skills in my resume. They are just a comma separated list. I don't even think that people take this stuff seriously. What matters most is always projects. If you feel like with just a small amount of research I could do most of what there is to do in Java, do something with it. Not just say you're "fluent in java" or whatever the bull crap that is. You're going to be a fresh grad. Projects will be a yes/no question for you, not a "wh-" question (unlike more senior developers). If you have something to show, you're golden. Also, Low level languages are C and C++. I don't even think your recruiter/boss/manager can program in assembly, even if s/he is a "lead/staff/senior embedded systems developer". They only teach assembly to students so that they have a better idea about what happens under the hood. There are a few select positions where you need to use assembly though. Highly unlikely travis will end up with one of these but perfectly possible. I wouldnt recommend learning it though unless out of curiousity. If you really need it for your job it will probably be something very specific which you will need to learn again anyways.
Am I right in guessing that you need it for reverse engineering?
|
Hyrule18968 Posts
Microcontroller programming uses it a lot as well
|
On January 08 2017 04:48 travis wrote:Show nested quote +On January 08 2017 00:52 RoomOfMush wrote:On January 07 2017 23:09 Djagulingu wrote:On January 07 2017 06:25 travis wrote:Okay I've got a question for the professionals out there on my resume, what sort of terminology should I use to explain how familiar I am with languages/systems? For example, I've been programming almost exclusively in Java, have finished 2 rigorous classes on it, and feel like with just a small amount of research I could do most of what there is to do in Java. But there's still lots to learn, of course. Would it be reasonable to say that I am "fluent in java" on my resume? Let's say I finish a large introductory text on python and learn all the concepts, and I am now capable of writing basic python programs. could I say that I am "familiar" with python? etc etc thanks  also, I am filling out an online application for an internship and they ask me "are you familiar with high and low level languages". I feel like the answer is obviously "no" since I don't know any low level languages. I do, however, have a basic idea of how assembly works.. But they are wanting me to actually know how to program in assembly / something comparable? You might rate yourself on your skills on a scale of 1 to either 3, 5 or 10. Also, nobody wants you to know how to program in assembly. I know how to do it and never had to use it for anything professionally. I don't rate my skills in my resume. They are just a comma separated list. I don't even think that people take this stuff seriously. What matters most is always projects. If you feel like with just a small amount of research I could do most of what there is to do in Java, do something with it. Not just say you're "fluent in java" or whatever the bull crap that is. You're going to be a fresh grad. Projects will be a yes/no question for you, not a "wh-" question (unlike more senior developers). If you have something to show, you're golden. Also, Low level languages are C and C++. I don't even think your recruiter/boss/manager can program in assembly, even if s/he is a "lead/staff/senior embedded systems developer". They only teach assembly to students so that they have a better idea about what happens under the hood. There are a few select positions where you need to use assembly though. Highly unlikely travis will end up with one of these but perfectly possible. I wouldnt recommend learning it though unless out of curiousity. If you really need it for your job it will probably be something very specific which you will need to learn again anyways. Am I right in guessing that you need it for reverse engineering? I dont know how much you would need it. It could certainly be helpful. Most of the work is done by algorithms though.
|
Hyrule18968 Posts
On January 08 2017 05:14 RoomOfMush wrote:Show nested quote +On January 08 2017 04:48 travis wrote:On January 08 2017 00:52 RoomOfMush wrote:On January 07 2017 23:09 Djagulingu wrote:On January 07 2017 06:25 travis wrote:Okay I've got a question for the professionals out there on my resume, what sort of terminology should I use to explain how familiar I am with languages/systems? For example, I've been programming almost exclusively in Java, have finished 2 rigorous classes on it, and feel like with just a small amount of research I could do most of what there is to do in Java. But there's still lots to learn, of course. Would it be reasonable to say that I am "fluent in java" on my resume? Let's say I finish a large introductory text on python and learn all the concepts, and I am now capable of writing basic python programs. could I say that I am "familiar" with python? etc etc thanks  also, I am filling out an online application for an internship and they ask me "are you familiar with high and low level languages". I feel like the answer is obviously "no" since I don't know any low level languages. I do, however, have a basic idea of how assembly works.. But they are wanting me to actually know how to program in assembly / something comparable? You might rate yourself on your skills on a scale of 1 to either 3, 5 or 10. Also, nobody wants you to know how to program in assembly. I know how to do it and never had to use it for anything professionally. I don't rate my skills in my resume. They are just a comma separated list. I don't even think that people take this stuff seriously. What matters most is always projects. If you feel like with just a small amount of research I could do most of what there is to do in Java, do something with it. Not just say you're "fluent in java" or whatever the bull crap that is. You're going to be a fresh grad. Projects will be a yes/no question for you, not a "wh-" question (unlike more senior developers). If you have something to show, you're golden. Also, Low level languages are C and C++. I don't even think your recruiter/boss/manager can program in assembly, even if s/he is a "lead/staff/senior embedded systems developer". They only teach assembly to students so that they have a better idea about what happens under the hood. There are a few select positions where you need to use assembly though. Highly unlikely travis will end up with one of these but perfectly possible. I wouldnt recommend learning it though unless out of curiousity. If you really need it for your job it will probably be something very specific which you will need to learn again anyways. Am I right in guessing that you need it for reverse engineering? I dont know how much you would need it. It could certainly be helpful. Most of the work is done by algorithms though. "Algorithms" is a thing that can be done in any language. This statement confuses me.
|
On January 07 2017 06:25 travis wrote:Okay I've got a question for the professionals out there on my resume, what sort of terminology should I use to explain how familiar I am with languages/systems? For example, I've been programming almost exclusively in Java, have finished 2 rigorous classes on it, and feel like with just a small amount of research I could do most of what there is to do in Java. But there's still lots to learn, of course. Would it be reasonable to say that I am "fluent in java" on my resume? Let's say I finish a large introductory text on python and learn all the concepts, and I am now capable of writing basic python programs. could I say that I am "familiar" with python? etc etc thanks  also, I am filling out an online application for an internship and they ask me "are you familiar with high and low level languages". I feel like the answer is obviously "no" since I don't know any low level languages. I do, however, have a basic idea of how assembly works.. But they are wanting me to actually know how to program in assembly / something comparable? On my own resume, I use "Comfortable with:" and "Familiar with:", and then provide a short list of languages. This takes two lines, and that's it. I more or less define comfortable to be that I can sit down and start being productive in the language immediately, while a language I'm familiar with is one I've used before, but would need some time/support to brush up on it again and get back up to speed.
On the other hand, I'm unsure of how closely anyone's even going to look at what languages you put down. If the language is actually important, and isn't something that it's ok to bootstrap as you start, then I'd think they'd be more interested in past professional experience or demonstrable skill through something else like projects.
I'd say it also depends a bit on where you're applying to. There's nothing stopping you from tweaking your resume to highlight different things depending on the company you're trying to work with. I think a good rule of thumb is to also try to highlight "soft" skills as well, to show that you've worked well in the past as part of a team, have leadership experience, etc.
|
On January 08 2017 06:00 tofucake wrote:Show nested quote +On January 08 2017 05:14 RoomOfMush wrote:On January 08 2017 04:48 travis wrote:On January 08 2017 00:52 RoomOfMush wrote:On January 07 2017 23:09 Djagulingu wrote:On January 07 2017 06:25 travis wrote:Okay I've got a question for the professionals out there on my resume, what sort of terminology should I use to explain how familiar I am with languages/systems? For example, I've been programming almost exclusively in Java, have finished 2 rigorous classes on it, and feel like with just a small amount of research I could do most of what there is to do in Java. But there's still lots to learn, of course. Would it be reasonable to say that I am "fluent in java" on my resume? Let's say I finish a large introductory text on python and learn all the concepts, and I am now capable of writing basic python programs. could I say that I am "familiar" with python? etc etc thanks  also, I am filling out an online application for an internship and they ask me "are you familiar with high and low level languages". I feel like the answer is obviously "no" since I don't know any low level languages. I do, however, have a basic idea of how assembly works.. But they are wanting me to actually know how to program in assembly / something comparable? You might rate yourself on your skills on a scale of 1 to either 3, 5 or 10. Also, nobody wants you to know how to program in assembly. I know how to do it and never had to use it for anything professionally. I don't rate my skills in my resume. They are just a comma separated list. I don't even think that people take this stuff seriously. What matters most is always projects. If you feel like with just a small amount of research I could do most of what there is to do in Java, do something with it. Not just say you're "fluent in java" or whatever the bull crap that is. You're going to be a fresh grad. Projects will be a yes/no question for you, not a "wh-" question (unlike more senior developers). If you have something to show, you're golden. Also, Low level languages are C and C++. I don't even think your recruiter/boss/manager can program in assembly, even if s/he is a "lead/staff/senior embedded systems developer". They only teach assembly to students so that they have a better idea about what happens under the hood. There are a few select positions where you need to use assembly though. Highly unlikely travis will end up with one of these but perfectly possible. I wouldnt recommend learning it though unless out of curiousity. If you really need it for your job it will probably be something very specific which you will need to learn again anyways. Am I right in guessing that you need it for reverse engineering? I dont know how much you would need it. It could certainly be helpful. Most of the work is done by algorithms though. "Algorithms" is a thing that can be done in any language. This statement confuses me. Presumably most of the lower level work in reverse engineering is automated? I wouln't know, because I know next to nothing about reverse engineering. When I was still interested in that kinda stuff, I mostly just tried to decompile stuff, took one look at the gigantic mess I was left with and gave up.
|
On January 08 2017 06:00 tofucake wrote:Show nested quote +On January 08 2017 05:14 RoomOfMush wrote:On January 08 2017 04:48 travis wrote:On January 08 2017 00:52 RoomOfMush wrote:On January 07 2017 23:09 Djagulingu wrote:On January 07 2017 06:25 travis wrote:Okay I've got a question for the professionals out there on my resume, what sort of terminology should I use to explain how familiar I am with languages/systems? For example, I've been programming almost exclusively in Java, have finished 2 rigorous classes on it, and feel like with just a small amount of research I could do most of what there is to do in Java. But there's still lots to learn, of course. Would it be reasonable to say that I am "fluent in java" on my resume? Let's say I finish a large introductory text on python and learn all the concepts, and I am now capable of writing basic python programs. could I say that I am "familiar" with python? etc etc thanks  also, I am filling out an online application for an internship and they ask me "are you familiar with high and low level languages". I feel like the answer is obviously "no" since I don't know any low level languages. I do, however, have a basic idea of how assembly works.. But they are wanting me to actually know how to program in assembly / something comparable? You might rate yourself on your skills on a scale of 1 to either 3, 5 or 10. Also, nobody wants you to know how to program in assembly. I know how to do it and never had to use it for anything professionally. I don't rate my skills in my resume. They are just a comma separated list. I don't even think that people take this stuff seriously. What matters most is always projects. If you feel like with just a small amount of research I could do most of what there is to do in Java, do something with it. Not just say you're "fluent in java" or whatever the bull crap that is. You're going to be a fresh grad. Projects will be a yes/no question for you, not a "wh-" question (unlike more senior developers). If you have something to show, you're golden. Also, Low level languages are C and C++. I don't even think your recruiter/boss/manager can program in assembly, even if s/he is a "lead/staff/senior embedded systems developer". They only teach assembly to students so that they have a better idea about what happens under the hood. There are a few select positions where you need to use assembly though. Highly unlikely travis will end up with one of these but perfectly possible. I wouldnt recommend learning it though unless out of curiousity. If you really need it for your job it will probably be something very specific which you will need to learn again anyways. Am I right in guessing that you need it for reverse engineering? I dont know how much you would need it. It could certainly be helpful. Most of the work is done by algorithms though. "Algorithms" is a thing that can be done in any language. This statement confuses me. When you compile things you just transform information from one model to "roughly equal" information in a different model. The process is usually not perfect though and some information is lost during the transformation. Reverse engineering is the process of reversing compilation. Transforming from the second model back to the first is difficult though because of that lost information I was talking about earlier.
However, there is a lot of information which can be "guessed" or deducted through statistical analysis, heuristics or simple brute force computational power. Todays computers are strong enough to reverse the process of compilation fairly well. You will never get an identical product (because names will be missing for most languages since they are not part of the compilation output) but you get something workable. Assembly is then no longer necessary because the output can be C or C++ or any other language you like.
|
I am learning python right now and I figured it would be easiest to just ask this here
If I make a list, listOne
and I say
listTwo = listOne
did I just assign a reference to listOne or did I copy the values?
|
Reference, but it's easy enough to test, and in general, get used to figuring out such stuff 
Try:
listOne = [1, 2, 3] listTwo = listOne listTwo[1] = "foo" print(listOne)
|
yeah I guess I could have just tested it, which I kind of did but not in a proper context
for the life of me I can't figure out what this program is doing
I am doing this little online coding game for fun and the question is to take a list of elements and return a list of non unique elements. for example [5, 5, 3, 2, 2] would return [5,5,2,2]
my code
def checkio(data): #Your code here #It's main function. Don't remove this function #It's used for auto-testing and must return a result for check. newlist = [] for k in data: newlist.append(k) templist = [] for n in newlist: if not n in templist: templist.append(n) newlist.remove(n) for j in data: if not j in newlist: data.remove(j)
return data
I'd expect this to work, and for some situations it does seem to, but when the test passes [1, 2, 3, 1, 3] I seem to return 1, 2, 3, 1, 3 back. which doesn't make sense to me
my thinking is that I make an empty list make a copy of data to play with
take 1 of each element in my copy, put them in my empty list and remove them from my copy
which should leave me with
data = [1, 2, 3, 1, 3] templist = [1, 2, 3] newlist = [1, 3]
then for each element in data, if it isn't in newlist, remove it
which should leave me with data = [1, 3, 1, 3]
but it doesn't.
what am I doing wrong? 
does the problem actually have something to do with concurrent modification?
disclaimer: I know there's probably methods to use and other ways that are probably easier. I'll find those out as I go along. Though if you want to tell me feel free 
edit 2. yay I solved it, I did this:
def checkio(data): #Your code here #It's main function. Don't remove this function #It's used for auto-testing and must return a result for check. copyList = [] for j in data: copyList.append(j) for n in copyList: if copyList.count(n) == 1: data.remove(n)
return data
and it looks like concurrent modification does mess it up so I can't modify a list as I iterate. is that something that tends to happen in all languages?
|
On January 10 2017 00:53 travis wrote:yeah I guess I could have just tested it, which I kind of did but not in a proper context for the life of me I can't figure out what this program is doing I am doing this little online coding game for fun and the question is to take a list of elements and return a list of non unique elements. for example [5, 5, 3, 2, 2] would return [5,5,2,2] my code
def checkio(data): #Your code here #It's main function. Don't remove this function #It's used for auto-testing and must return a result for check. newlist = [] for k in data: newlist.append(k) templist = [] for n in newlist: if not n in templist: templist.append(n) newlist.remove(n) for j in data: if not j in newlist: data.remove(j)
return data
I'd expect this to work, and for some situations it does seem to, but when the test passes [1, 2, 3, 1, 3] I seem to return 1, 2, 3, 1, 3 back. which doesn't make sense to me my thinking is that I make an empty list make a copy of data to play with take 1 of each element in my copy, put them in my empty list and remove them from my copy which should leave me with data = [1, 2, 3, 1, 3] templist = [1, 2, 3] newlist = [1, 3] then for each element in data, if it isn't in newlist, remove it which should leave me with data = [1, 3, 1, 3] but it doesn't. what am I doing wrong?  does the problem actually have something to do with concurrent modification? disclaimer: I know there's probably methods to use and other ways that are probably easier. I'll find those out as I go along. Though if you want to tell me feel free  edit 2. yay I solved it, I did this: def checkio(data): #Your code here #It's main function. Don't remove this function #It's used for auto-testing and must return a result for check. copyList = [] for j in data: copyList.append(j) for n in copyList: if copyList.count(n) == 1: data.remove(n)
return data
and it looks like concurrent modification does mess it up so I can't modify a list as I iterate. is that something that tends to happen in all languages?
Most languages. It's something you should avoid. Java outright doesn't allow it, hence why you haven't seen it before. The only situations in which it is okay to add/remove stuff in a list you are looping through if you loop through with a regular for loop rather than an iterator, and ensure your for loop ends at the end of the list despite your modifications. I *think* that with the way Python works, it is okay to remove elements that your iterator has already passed, but make extra double sure that that is actually true, and even then it's still best practice to not do that kind of thing, because it's just way too easy to send things going screwy when you decide to modify your code to work slightly differently.
|
Most of the time, you're much better off constructing a new list with all the good stuff instead of removing the bad stuff from the original list.
|
On January 10 2017 00:53 travis wrote: and it looks like concurrent modification does mess it up so I can't modify a list as I iterate. is that something that tends to happen in all languages? Whether concurrent modification is supported by a particular data structure depends on the implementation. If we take java as an example: The ArrayList and LinkedList do not support concurrent modification. This has technical reasons. The datastructures could be corrupted by concurrent modification. Instead of building in safeguards which make concurrent modification work they decided to disallow it. The safeguards would cost overhead of course and the devs argued that would not be a smart solution. Both of these data structures allow concurrent modification if you use an Iterator-Object though.
The CopyOnWriteArrayList on the other hand does allow concurrent modification in java. By design there is no possibility of corruption.
In other languages it is probably the same way. If concurrent modification can only be avoided at significant costs it is not supported. After all: the implementations of LinkedLists and ArrayLists are probably very similar in most languages.
Do as spinesheath said and use a new list. You could also save only the changes in the new list and then have them carried out after the iteration.
|
You could avoid manipulating lists yourself and hence avoid side effects altogether.
from itertools import groupby
a = [5, 5, 3, 2, 2]
counts = {k:len(list(v)) for k, v in groupby(sorted(a))} b = [x for x in a if counts[x] > 1] print(b)
The complexity is lower too.
|
|
|
|